Re: Sponsoring games in the git repository
On Tue, May 20, 2008 at 9:02 AM, Miriam Ruiz <firstname.lastname@example.org> wrote:
> Hi :)
> Although at some point I'll have to learn git, I haven't yet. Thanks a
> lot for filling http://wiki.debian.org/Games/VCS , but I still feel
> I'm not confident enough with it to get packages out of the git
> repository, tagging them and uploading to Debian, and I suspect that
> might also happen to other DDs in the Team. I mean, as git is
> something quite new, we're more used to SVN and know how to handle it,
> so it's quite no big deal right now to sponsor a game in the SVN
> repository for most of us. If would be great if we could have a quick
> recipe on the steps to tag and get a package ready from the git
> repository to be uploaded to Debian, to avoid the packages in git
> having it more difficult to be sponsored.
I don't think its such a bug issue for the final sponsoring, that
should just be a simple git-clone and check out of branch. In fact the
"Accessing a repository" section on http://wiki.debian.org/Games/VCS
is pretty much there. Assuming the origin/unstable branch is the
development tip and is at the point where the RFS would be made, after
a successful RFS you can just tag with the version number and continue
development on origin/unstable
The real problems can occur with patches and getting out of sync and
even creating loops in the commit history. There are ways of reverting
many things, but just sometimes a little more care is needed before
issuing a git-push to ensure you are where you think you are.
Often best to just get stuck in there ;-) thats what i did in
pkg-phototools but thankfully Cyril provided good git mentoring there.
Maybe if you are unsure run git and SVN in parallel until you are
happy for a given package?
I think after the initial learning curve, its got some really good benefits.
If i remember there are a couple of my favorite commands missing from
http://wiki.debian.org/Games/VCS that i will try to add. Being able to
generate patches from previous commits is nice. Being able to apply a
mbox of patches is cool too but may be not so relevant for the games
team? and my all time favorite, being able to revert commits and roll
back for when i have screwed something up locally and want to revert
before a push etc.