[SL-devel] GIT Migration

[Mitch Harder (aka DontPanic)]

I've been using GIT lately, and I like it.

But in the context of Sabayon-Linux, I'm not sure I can identify
anything that GIT does significantly better than SVN.  So that's
probably why nobody has been in a hurry to implement GIT.

To me, where GIT really shines is in large collaborations where you
need to manage and merge revisions from numerous different developers.

Also, GIT is probably not the right tool for handling binary files
such as artwork.

One of the neat things about GIT is that when you d/l a repository,
GIT has an efficient way of not only giving you a snapshot, but the
entire history also.  Your git directory is the same as the
developer's, with the capability of recreating the revision history at
any previous point.

For large collaborative projects on a code-base, this can be a really
neat feature.

But for handling artwork and other mainly binary files, this would be
a nightmare.

I also had to laugh when I saw "Entropy, has one core dev, we can set
him up an account easily".  But it does bring up a point that we would
have to put a certain amount of thought up-front into how your going
to restrict access.

It's not hard, but GIT is not like SVN and CVS that have their own
authentication mechanisms (although I think you can add that on to
GIT, but it's not the default).  From what I can tell, GIT just uses
standard linux account users and groups. You need ssh privilege (or
similar) to the server, and you have to either be the user or in the
group established for that git repository (assuming the group is
read/write on that directory), and you use standard linux filesystem
protections from there.

If you want to restrict access, you simply do it with user and group
permissions.

On Wed, Jan 28, 2009 at 2:52 PM, Ian Whyman <v00d00 at v00d00.net> wrote:
> The devs and core-beta have been talking about this for a long time,
> just thought I would bring up this subject again on ML as I'm not seeing
> any progress.
>
> As I see it the main challenges in moving to GIT are not hard to
> overcome:
>
> - Entropy, has one core dev, we can set him up an account easily
> - Overlay, Many, many users, in theory all we would need to do it
>  update our layman definition to the new git address, then all end
>  users would need to do is to remove and then add the repository
> - Installer, not sure how hard it would be to change the installer
>  update button, AFAIK the update install er button is broken currently
>  anyway so I don't see it as an issue.
>
> I also propose adding these items to git:
>
> - Art, having this centralised and distributed will improve turnaround
>  times and allow easier collaboration
> - Skel, same reasons as Art
> - sabayon-music, sabayon-mce and other sabayon hosted projects, we
>  should centralise all of our projects as it maintains organisation
>  and is easier to manage overall, keeping log of changes will make
>  them easier for other to maintain in future, if needed.
>
> As a test-case (and a if you want something done, do it yourself ll) I
> have set up a git repo to host sabayon projects on my server, currently
> it contains artwork and skel:
>
> GitWeb is at: http://gitweb.sabayon.hyperfish.org
>
> http address (for pulling)
> http://git.sabayon.hyperfish.org/artwork.git or skel.git
> git address (for pulling) git://git.sabayon.hyperfish.org/artwork.git
> or skel.git
>
> The address to pull from if you wish to push back up is;
> git://git@git.sabayon.hyperfish.org/artwork.git or skel.git before you
> are allowed to commit however you will need to send me a SSH2 public
> key and a list of what you want to access, so I can set up your access
>
> Ian "Thev00d00" Whyman
> _______________________________________________
> devel mailing list
> devel at mailman.sabayonlinux.org
> http://mailman.sabayonlinux.org/cgi-bin/mailman/listinfo/devel
>