[gst-devel] GStreamer switching to git

[Jan Schmidt]

On Thu, 2008-07-10 at 08:10 -0400, Sean Estabrooks wrote:
> On Thu, 10 Jul 2008 13:54:32 +0300
> "Ole André Vadla Ravnås" <oleavr at gmail.com> wrote:
> 
> > I'm aware that things are in heavy development, and that's really
> > promising. However, for those of us stuck doing GStreamer development
> > on this broken platform it's less of an option to put our current
> > efforts on hold, or reduce our productivity by having to fix bugs in
> > tools that aren't quite there yet. There's certainly enough
> > interesting problems to solve with the code itself on this platform,
> > and personally I'm already bogged down with maintenance of another
> > build system (because autotools isn't usable for day-to-day
> > development on Windows), and introducing even more tools that aren't
> > there yet on the portability-side will just make things even less
> > productive.
> 
> Git is a healthy project with lots of active development so things are
> improving all the time.  But that's not to say that the current version
> of Git on Windows is unacceptable.  Do you have any specific complaints
> against the current implementation?
> 

I've been trying out msysgit on XP this morning. The biggest stumbling
block by far seems to be support for ssh keys. It's an essential feature
for us (the only available access method to git.freedesktop.org), but so
far seems to only be support by either using the msys command line
client only, or by jumping through hoops to configure
Putty/Pageant/Plink as the ssh binary msysgit uses (I haven't yet been
able to get this to work, but I saw it working and am trying).

An alternate and very interesting option for the transition that Thadeu
mentioned is to configure a git-cvsserver on fdo. This allows (at least)
almost all the functions *I* need for working with GStreamer. It misses
the ability to tag/branch/merge, but I only do those because I'm doing
the releases. As far as I know, everyone else only checks out, updates
(possibly to a tagged revision), checks diffs and commits - and it seems
like a viable option for those. This would be a good way to completely
avoid the 'Windows' problem while the tools mature.

J.

-- 
Jan Schmidt <thaytan at noraisin.net>