dpkg-buildpackage environment export vs. debhelper

Raphael Hertzog hertzog at debian.org
Tue Nov 1 13:31:44 UTC 2011

On Tue, 01 Nov 2011, Colin Watson wrote:
> What I think we settled on as the least bad option is to refine the
> dpkg-buildpackage workaround so that it does not export environment
> variables if the package it's building is using debhelper compat level 9
> or above, and to manually review all such existing packages to make sure
> that they will continue to do the right thing given that change.  Such a
> change to dpkg-buildpackage would absolutely be a layering violation -
> dpkg-dev is not supposed to know about anything in debhelper - but it
> would at least be contained to the same paragraph as the existing
> transitional workaround so that it can be removed all in one go, it
> *reduces* the scope of the existing transitional workaround, and (if we
> ignore the deprecated DH_COMPAT) it can be written quite simply.

I agree that this is the sanest approach. And it's acceptable since it
will only last in precise... that said the precise packages are going to
last 5 years so it's quite likely that they will be used to build
much more recent packages (even if only backports).

Depending on how things evolve, it might make sense to also disable
it if Standards-Version ends up higher than a version of policy that
mandates dpkg-buildflags' usage (though I guess this is unlikely to happen

Raphaël Hertzog ◈ Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/

More information about the ubuntu-devel mailing list