Johannes Schauer wrote: > If you like that better, then I can also prepare a patch which uses > libdpkg-perl directly instead of copy&pasting the build profile evaluation > logic from it. Since debhelper already indirectly depends on libdpkg-perl > through dpkg-dev this additional dependency should not be a problem?
If you can do it without failing when debhelper is used with an older version of dpkg-dev, then that seems the right approach. Otherwise, it will make backporting debhelper harder. Maybe just avoid loading Dpkg::BuildProfiles unless DEB_BUILD_PROFILES is set? -- see shy jo
signature.asc
Description: Digital signature
