Bug#373807: [Pbuilder-maint] Bug#373807: one base.tzg per distribution

[martin f krafft]

also sprach Loïc Minier <lool at dooz.org> [2006.10.28.1546 +0200]:
>  Your wrappers are full or personal customizations.  I think a lot of
>  people are customizing their systems like this.

Exactly why I think we should move the feature upstream.

>  - this would make it rather hard to handle dist-upgrades of the
>    contents of the pbuilder (how do we detect a change from sarge to
>    etch?  should we rename the tarball after the upgrade?) or mixtures
>    of various distribution (how do you name a pbuilder which is setup
>    for sid + $company repository?)

this is up to you.

>  - this naming scheme is arbitrary, we could base the name on the login
>    of the unix user doing "sudo pbuilder create"

yup.

>  The most flexible approach remains (IMO) the current one where this is
>  simply configurable.

pbuilder has so many complexities that I just would not call it
simply configurable; you can do so much wrong. Even just command
line handling is a major PITA at times.

>  Out of curiosity: what's this "phoenix" shell you're using?

http://svn.madduck.net/pub/bin/base/phoenix

I exited the chroot too many times by accident. :)

-- 
 .''`.   martin f. krafft <madduck at debian.org>
: :'  :  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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pbuilder-maint/attachments/20061029/db1afc8d/attachment.pgp