[DRE-maint] Experiments with git

[Antono Vasiljev]

Excerpts from Lucas Nussbaum's message of Mon Jan 17 20:30:56 +0200 2011:

> > > svn-buildpackage wouldn't work with git.
> > > That's a -1000 considering that our current workflow deeply relies on
> > > svn-bp.
> > Ok. Let's think positive. What required in order to replace
> > svn-buildpackage with $OUR_SCRIPT_NAME.
> > Maybe git-buildpackage may be used?

> I think so, yes. All the docs refer to it, the new processes need to be
> defined, etc, etc. For what benefit? OK, git is faster, and I prefer git
> for new projects too.

It's easier to contribute and live in modern ruby world with git.
Almost all big ruby project use git. Why should we use svn? :)

Almost every ruby developer (potential package maintainer) is
already git user.

If we decide some day to keep upstream sources in tree it will
be much more easy with git.

As for me svn is pain in the ass.
 
> However, it is something that can be done at the same time as switching
> to gem2deb. So help make this happen, and we can do the switch to git at
> the same time, since gem2deb will force us to redefine all our processes
> anyway (with clear benefits).

I can make work on this. I need some mentoring from more
experienced debian developer. What parts of workflow are broken
without svn-buildpackage? What should be implemented?

I saw some checks made by svn-inject when I imported my
packages. I suppose this checks are first point in TODO.

Best wishes.
-- 
xmpp:self at antono.info
http://antono.info/
gopher://antono.info/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20110117/c586ebd3/attachment.pgp>