Neil Williams wrote: > where the program works at the point when it exits should be of no > concern to debhelper - it may be inside a chroot for some processes, > some outside. Why should debhelper get involved with that?
[EMAIL PROTECTED]:~/src/debhelper>grep debian/ Debian/Debhelper/Dh_Lib.pm|wc -l 28 > The other problem is that Debhelper::Dh_Lib cannot even be certain that > it is putting the log file in the right debian/ directory, even if one > exists - the autobuilder may have moved on to another package or 10 > before it exits. Trapping exit errors in a module is, IMHO, less than > ideal. All debhelper commands assume they run in the top-level directory of the source tree of the package to build. Dh_Lib is also not a general purpose library. It is intended only to be used in building debhelper programs. > Please reset the log behaviour so that it is, by default, off and only > enabled by specific executables, not modules. The logging is intended to also be done for third-party debhelper programs that use Dh_Lib as designed, such as dh_pysupport. Enabling it in each program individually is the wrong choice. > There could be a variety > of multi-build scripts out there that will break in this way. I cannot imagine why a non-debhelper program would have a good reason to use Dh_Lib. Nor that there are many such programs. Current guess at total number: exactly 1. This one should be fixed. -- see shy jo
signature.asc
Description: Digital signature
