Henrique de Moraes Holschuh <hmh@debian.org> wrote: > Well, I advocate adding the autotools-dev machinery to debian/rules > clean for this reason. It will cause the new config.sub/guess to be > propagated *to the source package*, so the GPL will not be violated. Nope. This will only work in normal uploads or NMUs, when the uploader could as well update the files herself (manually or ... see below). Autobuilders will not upload source packages. They will upload a binary built from a modified source that is available nowhere. What's worse, after the build log is purged, you won't even know for sure which version of autotools-dev was used, so there is NO sure way to reconstruct the source used. My proposition is to empower the maintainer (or a person doing a NMU) to check for up-to-date config.* scripts, and update them easily. The check part could be made in different parts of the infrastructure, depending on how obnoxious you want to get. Examples: * lintian warning or error * dpgk-buildpackage refuses to work with old scripts * dpkg-source -b refuses to bundle up old scripts And we could standardize on a "update-config-guess" target in debian/rules, that would copy the files to the right locations of the package. P.S. Why does libtool use this dreaded scripts at all? The concept of determining the system type to base some other decision on that seems severily broken to me, and goes against the spirit of autoconfiguration. -- Robbe
Attachment:
signature.ng
Description: PGP signature