Am 27.02.2010 um 22:58 schrieb Ryan Leavengood:
On Sat, Feb 27, 2010 at 4:32 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:Thanks for the explanation. Unfortunately svn doesn't help with this at all(AFAIK). I believe mercurial would, though.Or obviously Git, but it seems many Haiku developers are not fans of Git for whatever reason. I'd certainly consider using Mercurial though if we ever wanted to switch to a distributed version control system (which I think could be useful.)
I would think the issue is that Subversion has been around longer and more people know its command line options. Git, Mercurial and Bazaar (to mention that one as well) would all be new. To my knowledge and past experience, Git used to be the most suited for tracking an SVN repository - personally or for a future switch - whereas Mercurial only imported single snapshots rather than the complete SVN history.
Another part of the problem will be that the project layout is tailored to SVN, with lots of relatively independent components sitting in a huge tree. That way it's hard to find a free repository host, whether for personal branches like my signal stuff (btw, @Ingo thanks for the POSIX hint! still struggling...) or the official thing (1 GB minus the checked out files for r35495 with git-svn). If however for a new project (e.g., a port or an application) we'd start a new empty repository, then it pretty much boils down to personal taste and tool availability.
What's the status of Mercurial on Haiku? Last time I tried, it didn't work due to #2072 (Perl's socket.pm). Has that been resolved? It's needed for the Java port iirc.
Git is C-based and has little dependencies.Bazaar was a little more complicated due to Python bootstrapping, but appeared to work after Axel resolved the BFS issues uncovered by it. But similar tool problems probably still apply to svn itself, not having heard of an upstream merger of the apr and subversion patches?
Andreas
