On 15389 March 1977, Sean Whitton wrote:
Thus, it would be something of a layering violation if the normative part of Policy were to require or recommend using a particular tool to implement its other normative content.
Perhaps, though, there's no way for Debian to implement such a change other than amending Policy. It's not clear where else we would write such a thing down. The problem, I guess, is that we have never standardised on an implementation of Policy before now (aside from the bits that are in dpkg itself).
Well. We COULD "write" something down like it by having the archive check and reject anyting that doesn't fit... Ok, granted, thats kind of absolute and makes it really hard to ever have something better come up and get used, so isn't the prefered way, though we may start making it lintian based soft rejects for non-dh sometime, to help the stragglers.. But I agree that policy itself does not directly contain tool recommendations and don't think it would be best to start, at least in its main part. An appendix? Or another document, close to policy, that may get refered to from policy? -- bye, Joerg
