Heyya Arno, My reading of the policy is a bit different Changes in the Debian version of the package should be briefly explained in the Debian changelog file debian/changelog.[15] [..] To me, this means that we _should_ briefly explain all changes, not should have the file, since most tools will break without a d/changelog anyway. Technically, if I was to verbosely explain a change, I'd be in violation, if it were a _must_ :) Now, we need a policy that defines brevity ;) This might perhaps be better clairified, but I don't think § 4.4 contradicts § 12.7 at all -- in fact, it says to defer to § 12.7 for placement in the binary package, which is a must, so it must (therefore) exist in source. Cheers, Paul -- .''`. Paul Tagliamonte <paultag@debian.org> : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag
Attachment:
signature.asc
Description: Digital signature