Re: Orig tarball naming
-----BEGIN PGP SIGNED MESSAGE-----
On Friday 16 August 2002 23:27, Marc Haber wrote:
> On Fri, 16 Aug 2002 19:16:57 +0100, Paul Cupis <email@example.com>
> >On Friday 16 August 2002 18:10, Marc Haber wrote:
> >> I am wondering how cvs-buildpackage fits into this. From what I
> >> understand, cvs-inject checks in the unpacked upstream tarball into
> >> the CVS, puts an upstream_version tag on it. cvs-buildpackage then
> >> creates the orig.tar.gz from the CVS sources. Isn't that a violation
> >> of the pristine sources principle?
> >I don't think it creates the orig.tar.gz from CVS _if_ the orig.tar.gz
> > already exists in the parent directory or the build directory.
> Looks like I'll have to say goodbye to my practice of building in a
> virgin changeroot, or that I'll have to modify my scripts to put the
> upstream tarball where cvs-buildpackage expects it to be :-(
It will contruct a chroot system for you, and can easily build a packge from
source in the chroot system (easily as in a single command). And it looks for
the orig.tar.gz and automatically moves it into the chroot, honouring the
upstream orig.tar.gz and solving this problem.
You just have to copy the created files out of /var/cache/pbuilder/result (or
wherever) and sign the .dsc and .changes files with debsign.
It works wonders, and you can have multiple chroot systems set up (woody,
sarge, sid) for example, specifying which one to use on the command line et
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----