Re: [B2-devel] git?

[Alexander v. G. <kal...@un...>]

On 16.06.2012 04:08, Christian Bauer wrote:
> Hi!
>
> At last some action here. :-)
>
> I agree that for a project with so few active developers CVS should
> still be sufficient. But if it helps people working on the code I will
> gladly convert the CVS repository to git and put it on GitHub (and shut
> down the CVS).

Don't even have to use git... Subversion, Mercurial, all good choices.
I simply am using git because it is a little more 'unixy' then Mercurial.

> My main concern is what to do with the files shared between B2 and SS. I
> guess the best starting point would be to put both projects into a
> single repository, including the symlinks, and eventually rework the
> directory layout later?

I think that would be a positive thing.  While I can easily see the 
reasoning
behind using the symlink scripts, given the "mature" state of each codebase
the current commits are minimal.

I'd vote to do as you said for sheepshaver and keep B2 as-is. Maybe someday
SS could do what B2 does and then you could drop B2 completely :)

> As far as the crappy GTK prefs editor is concerned: If I was starting
> from scratch I'd implement it with Qt (in C++, not with Designer) and
> make it work on all supported host platforms. The current code was
> originally a quick'n'dirty port of the BeOS UI...

Haha, yeah.  It's pretty easy to tell that not a lot has changed from a
necessity standpoint (SS is mature, and the current pref editor "works")

I actually have SheepShear compiling now on Haiku as of last
night, however linking is another story :)

  -- Alex