Guillem Jover <[email protected]> writes: > Ah! I think I see what you mean now. Would the attached patch fix the > confusing text? > > diff --git i/man/dpkg.pod w/man/dpkg.pod > index 8349f0afd..001373b75 100644 > --- i/man/dpkg.pod > +++ w/man/dpkg.pod > @@ -1438,8 +1438,8 @@ During normal operation, this variable is empty. > When installing packages into a different B<instdir>, B<dpkg> > normally invokes maintainer scripts using L<chroot(2)> and leaves > this variable empty, but if B<--force-script-chrootless> is > -specified then the L<chroot(2)> call is skipped and B<instdir> > -is non-empty. > +specified then the L<chroot(2)> call is skipped and > +this variable is set to B<instdir> (which will be non-empty). > > =item B<DPKG_ADMINDIR>
Hi Guillem, Yes, this is pretty much what I expected, thanks for confirming it! I wouldn't even add the "(which will be non-empty)" part to avoid questions arising from arguments like --root='', but anyway. > (I also noticed that there's no documentation for dpkg honoring > DPKG_ROOT and DPKG_ADMINDIR being set when it runs, which was a > recentish behavior change, will document that too.) Thanks for taking care, that sounds like an important point indeed. -- Regards, Feri.
