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

Re: Anyone using CVS or PRCS?



On Tue, Jul 14, 1998 at 10:57:41AM -0500, David Engel wrote:
> I'm thinking of using CVS or PRCS on my Debian packages to help me
> keep my own and third-party patches straight.  Is anyone else doing
> this, and if so, how do you make it work with the Debian source
> packaging system?  For example, Debian policy wants the toplevel
> source directory name to contain the version number while CVS uses the
> module name without a version number instead.  Also CVS adds
> bookkeeping directories and files that dpkg-source will include in the
> .diff.gz file.
> 

I use cvs-buildpackage successfully with my packages:

Package: cvs-buildpackage
Priority: optional
Section: devel
Installed-Size: 74
Maintainer: Manoj Srivastava <srivasta@debian.org>
Architecture: all
Version: 1.14
Depends: dpkg-dev (>= 1.4.0.9)
Filename: dists/frozen/main/binary-i386/devel/cvs-buildpackage_1.14.deb
Size: 35230
MD5sum: 3808f22792982bfc832bbdacf3f4f2c5
Description: Debian package scripts for CVS source trees.
 This package provides the capability to inject or import Debian
 source packages into a CVS repository, build a Debian package from
 the CVS repository, and helps in integrating upstream changes into
 the repository.
 .
 The import or inject process takes a dsc (Debian source control)
 file, and imports it into CVS. The module path can maintains
 distribution and section information; for example, one may inject
 hemm/hemm/devel/make into the repository.
 .
 The build process works analogously to dpkg-buildpackage, and can be
 used from within the checked out source tree, or with additional
 information, can be used from anywhere. In the latter case, you can
 build any previous version of the package, as long as the
 corresponding orig.tar.gz file is still around. The build script
 checks out the relevant version from the CVS repository, and runs
 dpkg-buildpackage to create the Debian package.
 .
 Combined, these utilities provide an infrastructure to facilitate the
 use of CVS by Debian maintainers. This allows one to keep separate
 CVS branches of a package for stable, unstable, and possibly
 experimental distributions, along with the other benefits of a
 version control system.
 .
 This can be used to generate a unified CVS source tree, for example.

Greetings,

				Christian
-- 
Christian Meder, email: meder@isr.uni-stuttgart.de
 
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks for the swallows, 
It sets the sand a-blowing,
And the blackberries a-growing.
                      (Henry David Thoreau)
 


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: