On Tue, Jan 17, 2006 at 09:39:20PM -0500, Justin Pryzby wrote: > Package: lintian > Severity: wishlist > > Policy 4.8: > | If a build file is touched at the end of the build target, as > | suggested above, it should be removed as the first action that clean > | performs, so that running build again after an interrupted clean > | doesn't think that everything is already done. > > It would be great if lintian could check for this.
I've looked into this a bit. I'm not sure yet how to implement this best. One needs essentially three bits of information for this: 1) The contents of the build and build-stamp targets 2) The contents of the clean target 3) The debhelper compat level Currently the first two are collected in checks/rules and the last one in checks/debhelper. Neither of these two is a entirely trivial task. Maybe we need a collection/debhelper script? I have the feeling that this will at some point benefit many source oriented check scripts. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
