Raphael Geissert <[email protected]> writes: > While working on the check for prebuilt binaries in source tarballs I > was thinking about making it severity: minor as having prebuilt binaries > around may cause make to believe it doesn't have to anything on them. > Those cases are usually alleviated thanks to the call to debian/rules > clean, but just to make sure prebuilt binaries are not accidentally > shipped, I think it would be a good idea to check for binaries belonging > to another architecture other than the one specified in the binary > control file. Of course binaries in multi arch directories should be > ignored, but I can't think about any good reason to for example ship an > i386 binary in an armel package.
One does that sort of thing for cross-compilation support packages, but they normally use recognizable special directories. Sure, that sounds like a good check; it's no more prone to false positives than the existing check for binaries in arch: all packages (which has the same problems). -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
