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

Re: creating an orig.tar.gz from a CVS



Hello List:

Thanks Xavier for the trick.

After getting information from the upstream maintainer, it appears that the CVS have
a dedicated Makefile to build the upstream package. Of course, this Makefile is not
distributed within the upstream package, as other part of the CVS tree: the package
is full of makefile mostly written by hand (meaning not generated with automake) that
are meant to run on different OS. In short, it is a little messy and the debian/rules
trick can not be applied here because the CVS tree source includes the package, but
is not the package. Never mind, this certainly part of the job of the Debian maintainer
to rationalise as far as possible the upstream package in view to apply the dh machinery.

Cheers,
Jerome
On 06/02/12 15:00, Xavier Grave wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 02/02/2012 22:43, Jerome BENOIT a écrit :
In short, I have to do it by hand.

You can still add a target in your debian/rules file to avoid doing it
too many times :). See [1] for explanation for example about
get-orig-source target.

xavier
[1] 4.9 in http://www.debian.org/doc/debian-policy/ch-source.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPL9zqAAoJEG3iFwasTcfat/MP/A/EdEYe83zuisWheJa5Okgr
kriYeGuNMTPjVpyNrpA6EqY/6OL+SV54i2p+7EzuJDSU7jtalG9+PMvP5uD4AmM/
h0ds2sMsM6BASBysmjJ15g0/gTPLewRKZEQ4xcdV6sOtw1jXfk+vPe4tV8z9v4gf
v1SvGB/LPFAJrRDgCi32ZeWKPG9G6pmCC/NJir4DCT3IO2yq30dn7ep3Oz9bcHba
pvVDn6ZlUZ74s4/8XZz/xmOGX3ScuTX0/k3BtPBa9pEtle/Hws/waz6C7F66ULMa
mr+FARrCyLAHvr01lGYxC8/yxms++yq7blBpktQFkJwmrFh5Mp6L25bw/EPDaTtz
KaSXXVjcf2vUbNV9w0NKq2KGj+zQ1Qk0bOVvsKXjJ/t62zBdrlGF73qhbHDCHJlu
v63kggr4roqax61ISCddS6kZ6KBKTZ/REroVCq+drNHCziouNK8lFqvzAPjCdR1m
lklStiu3GbJ+7mVBRqY0yMr5uyNAEeneOFhFbjCMJwg4gNwkR7xV4Q5Eseyy5ACG
eEVfn/JXfJ0pziefBLNf3/Rn6Cxjh2itIYhjD/6QS4R84YxYPCYOrQDxZHbY6r+T
EicWbkpt60JJggKwhqBoKdkcvbR+ngCowcYJYF4gkm83UVIgGgfIshj8/Ndd0X5f
OCbVp4BpXUDPs73xskWg
=WdQp
-----END PGP SIGNATURE-----


Reply to: