Re: Anyone using CVS or PRCS?
"David Engel" <david@ods.com> writes:
> 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 just started to do this with my own packages, and I have used it in
the past to update existing packages to new upstream versions. You
want to look at "cvs-buildpackage" which has scripts to automate
everything.
The "cvs-buildpackage" package contains the "cvs-inject" to enter an
existing Debian package into cvs, and "cvs-upgrade" to merge in new
upstream source.
It also contains the "cvs-buildpackage" script which, when run in a
checked out CVS tree, will "export" the original code and the latest
code to a (different) working directory and run "dpkg-buildpackage".
(When you "export" stuff, it leaves out the CVS directories and you
can tell it what directory name to export it into.)
There is a Debian CVS howto at:
http://www.debian.org/devel/HOWTO.cvs
and in /usr/doc/cvs-buildpackage. But they are out of date (they tell
how to do the "cvs-inject" stuff manually).
I've learned the most from running cvs-inject and cvs-upgrade with the
"-n" options and looking that the command lines that they use. If you
(like me) are not familiar with CVS branches et al, it's a good idea
to try updating a existing packages to new upstream source with
cvs-inject and cvs-upgrade to get a feel for how everything works.
Steve
dunham@cps.msu.edu
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: