Sorry about the env var confusion -- in fact $ENABLE_DBGSYM is an internal variable in dh_strip, so that's definitively wrong. $DH_BUILD_DDEBS is still present in our version of debhelper:
$dh{ENABLE_DBGSYM} = 0 if not $ENV{'DH_BUILD_DDEBS'};
but got dropped in Debian, so let's not use that either. The manpage documents
The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS
environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure
that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible).
So let's use that then?
> We'll probably have to keep /CurrentlyBuilding around for a while.
Yes, indeed. At some point we might consider SRUing the testing of DEB_BUILD_OPTIONS to stable pkgbinarymanglers/pkg-create-dbgsyms, but let's first let this bake a while. Until then our debhelper should test /CurrentlyBuilding too.
Sorry about the env var confusion -- in fact $ENABLE_DBGSYM is an internal variable in dh_strip, so that's definitively wrong. $DH_BUILD_DDEBS is still present in our version of debhelper:
$dh{ENABLE_ DBGSYM} = 0 if not $ENV{'DH_ BUILD_DDEBS' };
but got dropped in Debian, so let's not use that either. The manpage documents
The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS
reproducible) .
environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure
that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit"
So let's use that then?
> We'll probably have to keep /CurrentlyBuilding around for a while.
Yes, indeed. At some point we might consider SRUing the testing of DEB_BUILD_OPTIONS to stable pkgbinarymangle rs/pkg- create- dbgsyms, but let's first let this bake a while. Until then our debhelper should test /CurrentlyBuilding too.