[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FWD: [Bug#528733: O: svn-buildpackage -- helper programs to maintain Debian packages with Subversion]



On Fri, May 15, 2009 at 12:54:43PM +0200, Manuel Prinz wrote:
> Am Freitag, den 15.05.2009, 17:40 +0900 schrieb Charles Plessy:
> > it looks like we may have one more reason to explore other version control
> > systems.
> 
> Neil Williams adopted it. Nevertheless, I think your statement still
> holds. I'm not sure if I can attend DebConf but maybe we can gather some
> interested people and talk about experiences with other VCSs there?

IMHO this problem has two sides:

  1. Do we really *depend* from svn-buildpackage to *use* SVN as
     our repository?
     My answer is: Not really even if svn-buildpackage is kind of nifty.
     I personally don't use svn-buildpackage because I was to lazy to
     find out how to smoothly use it with pbuilder.

  2. Do we really need to investigate other VCSs?
     My answer is: No, just lets take git *IN* *CASE* we want to replace
     SVN.  The rationale behind it is that if you observe the "market"
     several projects seem to use git and if I'm not mistaken Git has the
     largest adoption rate in Debian.  I know that different people have
     different pet-VCSs and might swear that they can't imagine to live
     without it.  But I regard team work as adapting habits of a team and
     it seems that several members of the Debian Med team are even actually
     using Git.  So the choice to what we should move is IMHO just done.

Please try not to turn this thread into an Emacs-agains-Vim-ish flamewar
about the "best" VCSs.  There is no such thing like a best VCSs (neither
there is a "best" editor).  There is only a "fits good for *our* purpose"
(the difference between the editor choice is that you can s/our/my/ - and
this is actually an important difference, because choosing an editor is your
very own choice but choosing a VCS involves more people).

So I would consider it as valid approach to follow the style of Debian Science
to provide SVN and Git as options.  This leaves enough room for experimenting
and enables me to stay with SVN as long as my bandwidth at home became
acceptably fast to pull large upstream code chunks (which is in my eyes the
worst thing in Git - but this is my personal problem).

Kind regards

       Andreas.

-- 
http://fam-tille.de


Reply to: