CVS source trees and Debian
Hi folks,
I am pleased to announce a new version of cvs-buildpackage
that has significant new functionality. For example:
find /var/spool/mirror/debian/hamm/hamm/source \
-type f -name \*.dsc | while read i;
do
j=$(dirname $i | sed -e s:source/:: \
-e s:/var/spool/mirror/debian/:: )
cvs-inject -M$j $i
done
manoj
excerpts from the manual pages follow
______________________________________________________________________
NAME
cvs-inject - inject a debian source package into a CVS
repository
SYNOPSIS
cvs-inject [options] <package>.dsc
DESCRIPTION
This manual page explains the Debian cvs-inject utility,
which is used to inject or import Debian source packages
into a CVS repository. It handles Debian--only packages
(which do not have diff files) as well as normal packages
from upstream sources converted to Debian use.
The upstream sources are imported to the vendor branch and
tagged upstream_versions_<upstream version> with all dots
translated to under scores. The debianized sources, if
different, are put on the main branch, and tagged
debian_version_<upstream version>-<debian revision> with
all dots translated to under scores.
The sole argument is a debian source .dsc file, which is
parsed to get the package name and version. cvs-inject
reads the same config file /etc/cvsdeb.conf as the the
other cvs-* utilities do. People may use of the dry run
option to inspect the steps this utility takes.
Combined with the companion utilities cvs-buildpackage and
cvs-upgrade, this provides an infrastructure to facilitate
the use of CVS by Debian maintainers. This allows one to
keep separate CVS branches of a package for stable, unsta
ble, and possibly experimental distributions, along with
the other benefits of a version control system.
This utility can be used to generate a unified CVS source
tree, for example, with
find /var/spool/mirror/debian/hamm/hamm/source \
-type f -name \*.dsc | while read i;
do
j=$(dirname $i | sed -e s:source/:: \
-e s:/var/spool/mirror/debian/:: )
cvs-inject -M$j $i
done
Which happily gobbled up the sources and created a CVS
repository on my machine until the partition filled up.
______________________________________________________________________
NAME
cvs-buildpackage - build Debian packages from a CVS repos
itory.
SYNOPSIS
cvs-buildpackage [options]
DESCRIPTION
This manual page explains the Debian cvs-buildpackage
utility, which is used to build Debian packages whose
sources are stored in a CVS repository. This is a CVS
-aware wrapper around dpkg-buildpackage, and it first
parses ./debian/changelog; exports the corresponding ver
sion (tagged debian_version_<$version> ), and runs dpkg-
buildpackage in the exported tree. If this utility is not
run from a top level directory of a checked out Debian
package source tree, for example, to build an old version,
the cvs module name, or the package name have to be sup
plied on the command line.
Combined with the companion utilities cvs-inject and
cvs-upgrade, this provides an infrastructure to facilitate
the use of CVS by Debian maintainers. This allows one to
keep separate CVS branches of a package for stable, unsta
ble, and possibly experimental distributions, along with
the other benefits of a version control system.
______________________________________________________________________
NAME
cvs-upgrade - upgrade a debian source package kept in a
CVS repository
SYNOPSIS
cvs-upgrade [options] <package Name> <Upstream Version>
[<debian revision>]
DESCRIPTION
This manual page explains the Debian cvs-upgrade utility,
which is used to upgrade Debian source packages in a CVS
repository. It expect a properly conditioned new upstream
sources in the work directory
The upstream sources are imported to the vendor branch and
tagged upstream_versions_<upstream version> with all dots
translated to under scores. At this point the cvs-upgrade
utility pauses automatic actions, since manual interven
tion is required to resolve any conflicts that may have
occured. It reminds the user about checking out the
sources, resolving conflicts, and tagging the debianized
sources, with debian_version_<upstream version>-<debian
revision> with all dots translated to under scores.
It expects the package name, upstream version, and , if
relevant, the Debian reviosion on the cmmand line. I also
expects to find a properly conditioned new upstream
sources file in the .orig.tar.gz format in the working
directory.
cvs-upgrade reads the same config file /etc/cvsdeb.conf as
the the other cvs-* utilities do. People may use of the
dry run option to inspect the steps this utility takes.
Combined with the companion utilities cvs-buildpackage and
cvs-upgrade, this provides an infrastructure to facilitate
the use of CVS by Debian maintainers. This allows one to
keep separate CVS branches of a package for stable, unsta
ble, and possibly experimental distributions, along with
the other benefits of a version control system.
______________________________________________________________________
--
Ask not what you can do for your country, but what your country's
been doing to you. Avengers
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: