On Sun, 29 Jun 2003 22:43:17 +0200, Marc Haber <[EMAIL PROTECTED]> wrote: [creating foo-patched .deb from foo .deb unmaintained by the upstream or the Debian maintainer] > How would more experienced Debian maintainers handle this issue? There are some tools which unpack and/or patch the source at build time. * debnest: unpacks a Debian style upstream source (.orig.tar.gz, .diff.gz and .dsc in a tarball) * cdbs: a set of Makefile fragments such as - autotools.mk: calls ./configure with right arguments (--prefix, --mandir, ...) - debhelper.mk: calls dh_* auto-magically cdbs includes simple-patchsys.mk, which applies patches at build time and unapplies them at clean time * dpatch: executes scripts (not diff files) in debian/patches at build or clean time * dbs: unpacks a tarball-in-tarball and patches the unpacked source dbs does nothing at clean time because you just remove the source tree
The best way is to put source files of foo .deb in a tarball and use that tarball as the "upstream" source of foo-patched .deb, unpacking it with debnest. cdbs or dpatch will help you if you modify the non-Debian part of the source a lot. -- Oohara Yuuma <[EMAIL PROTECTED]> Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Er, let's get into all the messes of the parliament. --- shinichiro.h, diary 2003/3/24 "parliamentary bullet-dodging system"