Re: Games Team now has git repository
2008/5/15 Andres Mejia <email@example.com>:
> I've submitted a request for a directory under git that the games team can
> use. It's already been fulfilled. The directory is under /git/pkg-games in
> the alioth servers.
Cool, now the experiments with git can start. I'll repeat what I wrote
in January about that , so that it could be open for discussion
1) Someone has to explain briefly but clearly, preferably in a wiki
page, the minimal steps how to obtain the latest sources from the
repository and how to upload modifications to them, so that it won't
be a problem for newbies to join the team. I myself don't know much
about handling stuff in git or bzr either.
NOTE: We need a clear recipe that should work for both git or svn in
the context of
the team, not just a generic tutorial on git. [1a]. It should also be
clear enough to make life easier for sponsors.
2) I'd prefer to experimentally handle just a few packages at first,
and with just one other system than svn for the moment (not git and
bzr at once). It might be a good idea to handle some newer packages in
git just to get an idea about whether it would work or not, but it
could be OK to move some few packages from svn too anyway if it's
really wanted. As I said, it should be done in a way that anyone in
the team would be able to work on them too, that means the wiki page
NOTE: Joey Hess said that he might be willing to offer up kobodeluxe,
which is in git. [2a]
3) From what I've seen, the idea might not really be to move to a
newer versioning system, but to have different repository systems at
once. I don't really consider this to be a huge problem (as long as
the basic howto is documented, as I said), but it might make it harder
to implement ACLs (if desired) in the future or things like that, so
I'd like to have an open discussion on the pros and cons about having
one single system vs. multiple ones at some point.
4) If at any point someone would need to download all the packages to
do some general modification (like that with about the Homepage, for
example), we could prepare a set of scripts to do so. With some small
scripts the system should be able to download all the packages from
the different versioning systems, or upload the changes to all of
them. Ideas on this?
NOTE: Joey Hess explained how this could be done with .mrconfig [4a],
I personally dunno about it
5) I'd prefer if similar packages shared the same versioning system
and repositories, for example all Kenta Cho's games should be handled
in a similar way, all Quake-related stuff that might be considered to
be related, and so on.
6) As Vincent said, each package should be in just one repository. No
redundancy allowed, as it would only be a source of problems.
NOTE: If one package migrates from one to the other, the old VCS
should be cleaned up. [6a]
7) If we move packages from a versioning system to another, I don't
want their history and logs to be lost. Is it possible to do so?
> For those who don't know how to use git well, look at
> http://wiki.debian.org/Alioth/Git. I've created a symlink to
> that 'setup-repository' script that's mentioned in the wiki.
Thanks, that will be really useful :)
BTW, will commits to git also be reported to the commits mailing list?
PS: Previous discussion on this topic:  , starting on