control: tags -1 confirmed >>>>> "Johannes" == Johannes 'josch' Schauer <[email protected]> writes:
Johannes> Hi,
Johannes> since dpkg 1.18.5, dpkg sets the variable DPKG_ROOT when
Johannes> invoking maintainer scripts. Usually that variable is
Johannes> empty but when calling dpkg with --root and
Johannes> --force-script-chrootless, dpkg will set DPKG_ROOT to the
Johannes> new root directory. In that mode, maintainer scripts are
Johannes> called without chroot(1) around them, and thus have to be
Johannes> able to possibly operate on the path from DPKG_ROOT
Johannes> instead of working on /. This is useful for bootstrapping,
Johannes> creating chroots for foreign architectures where utilities
I spoke to Johannes and Helmut today.
Steve, I think we should take this patch and will do so unless you
object if I'm the next to upload.
I found the foreign architecture use case compelling.
There are cases where qemu has not been available or where it's been
horribly slow in the early architecture bootstrap phase, even for
architectures that Debian clearly cares about.
So even using a conservative definition of what architectures we care
about , we cannot always usefully rely on qemu for bootstrap.
According to Helmut roughly build-essential needs to support this for
the bootstrap case (and some of those packages do not have maintainer
scripts).
According to Johannes there are roughly 11 packages including pam that
still need to be patched.
So, the feature seems achievable for a significant important use case
and so I think we should take the patch.
I'm less convinced by some of the other arguments. Helmut, Johannes and
I are continuing to chat about that offline, but I think it has no
impact on PAM.
signature.asc
Description: PGP signature
