[Pkg-firebird-general] Fw: Re: packaging and CVS on alioth

Grzegorz B. Prokopski gadek@debian.org
Sun, 13 Jun 2004 17:31:40 -0400

Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: quoted-printable

W li=B6cie z nie, 13-06-2004, godz. 16:56, Remco Seesink pisze:=20
> Hello,
> We need to decide if we want to use Subversion or CVS for version control=
 of the
> packaging. Personally I have no experience with SVN, but that's more a re=
ason in
> favour for it for me. I'd like to learn it.
> What do you all think?

There's no question about that :)  We should go with SVN.  It takes max
10 minutes to learn for somebody who knows CVS.  And you will never ever
want to get back to CVS (speaking from experience - I *hate* CVS since
I started using Subversion; CVS is so big PITA!).

In particular SVN is:
* actively developed,
* works *perfectly* under windows and linux, *BSD...,
* already has many (also graphical) tools available,
* allows for much greater flexibility and *COMFORT* while developing
* includes much better mechanisms than CVS that allow many developers to
work on one piece of software simultanously, because
* branches are *cheap* and not broken like in CVS.

You might also want to take a look at the "Why subversion" part of:


I've been using Subversion since over a year and really, if we have
choice between CVS and SVN, the answer can be just one. :-)

Remco, before doing the first import to Subversion repository,
could you please show up on #sablevm (or #debian-devel) so that we could
make sure we have sane repository structure?  I have some experience
maintaining and developing software, which has its upstream
elsewhere, in SVN.  In particular the "just throw our version into SVN"
might not be the best idea.  I am on #sablevm/#debian-devel everyday,
most of the time.


				Grzeogorz B. Prokopski

PS: Thanks Remco for finding out what are the possibilities.
I think with Subversion we can safely just keep the whole Firebird
tree in SVN.  As long as people do NOT use "import" nor "add" to
work on separate branches, but do "copy" of an existing versions
to start their own branches - this is very cheap, fast and robust.

See the link above for more informations about usage of SVN and
the really great:

* Subversion Book http://svnbook.red-bean.com/
  (especially the section "Subversion for CVS users" at
    http://svnbook.red-bean.com/svnbook/book.html#svn-ap-a )
Grzegorz B. Prokopski      <gadek@debian.org>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://devel.sablevm.org/wiki/Features

Content-Type: application/pgp-signature; name=signature.asc
Content-Description: To jest =?iso-8859-2?Q?cz=EA=B6=E6?= listu podpisana

Version: GnuPG v1.2.4 (GNU/Linux)