On Wed, 2003-09-24 at 11:47, Raphael Hertzog wrote:
> Le Wed, Sep 24, 2003 at 11:12:26AM +0100, Ross Burton écrivait:
> > > 4- CVS/SVN usage :
> > > ------------------
> > >
> > > Akira TAGOH has proposed to create a module for each source-package (the
> > > module name is the name of the source package) with the debian dir
> > > included. We could include the whole package for the native ones and
> > > doc for example.
> >
> > I like the idea of the full upstream source in CVS, as it should make
> > things easier. However, I've never actually done this, has anyone else?
>
> Considering the size of Gnome I doubt this is a good idea. Better only
> maintain the debian directory with SVN/CVS. Of course, the debian dir
> should be the only change to the upstream source. That means all
> packages should use a system like dpatch to be able to modify the
> upstream sources.
Thats a good point. Are there tools to make managing just debian/ in
CVS easy, or should we write some as we go?
> A convention to avoid mistakes is to use the new version but indicate
> "UNRELEASED" instead of unstable to avoid unwanted uploads.
>
> Suppose current unstable version is 1.2-1 and you want to work on the
> next upload which is planned to be 1.2-2 you just put this in the
> changelog :
> mypkg (1.2-2) UNRELEASED; urgency=low
>
> * Maintainer One
> - Change 1
> - Change 2
> * Maintainer Two
> - Change 1
> - Change 2
>
> And when you're ready to upload you just s/UNRELEASED/unstable/ and
> you're done.
Looks good to me, the UNRELEASED trick is nice.
Ross
--
Ross Burton mail: ross@burtonini.com
jabber: ross@burtonini.com
www: http://www.burtonini.com./
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Attachment:
signature.asc
Description: This is a digitally signed message part