Don Armstrong <[EMAIL PROTECTED]> writes: > It was tightened about 2 or 3 years ago, iirc.
> Regardless, even requiring debian/rules to be a makefile doesn't > actually do much, because someone could do something like: > .DEFAULT: > debian/irule $@ > or whatever. > People should be using make, but if they have a valid reason for doing > something else, policy shouldn't get in the way. I suppose that's true. Okay, we can at least explore the option of double-checking that Policy specifies everything that we're assuming make will do and that the rest of the project assumes. Does the current Policy text have enough details (with a strong enough requirement) around arguments, exit status, and so forth that something written exactly to Policy would behave like a makefile to every other part of the project? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
