also sprach Loïc Minier <[EMAIL PROTECTED]> [2006.10.22.1606 +0200]: > I had the same problem than you, and ended up using this shell snippet > in my pbuilderrc: > > # archived chroot image location > if [ "$PDEBUILD_PBUILDER" = "pbuilder" ]; then > BASETGZDIR="$PBUILDERROOT/basetgz/$DISTRIBUTION" > create_dir "$BASETGZDIR" > BASETGZ="$BASETGZDIR/base.tgz" > fi > > /usr/share/doc/pbuilder/examples/pbuilder-distribution.sh is another > solution. > > Do you agree this feature can be handled by end-user configuration?
Certainly. I've been using http://svn.madduck.net/pub/bin/pbuilder/plogin, which can be symlinked to pexecute, pbuild, pupdate, and pclean. Those five take care of my pbuilder needs. To build packages, I use pbuild, or, if that's not available, the same sort of idea in dbuild: http://svn.madduck.net/pub/bin/debian/dbuild. (updates to these pending, I am on the train now and rewrote parts) > Should be keep the bug open? Well, it kinda depends. I think it's always nice to get rid of wrapper shell scripts as functionality moves to the core -- pbuilder in this case. If it won't get fixed, tag it wontfix. Okay? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
