On Wed, Oct 04, 2017 at 03:30:37PM +0200, Mattia Rizzolo wrote: > Package: debian-policy > Version: 4.1.1.0 > > Policy ยง 5.6.11, after describing the meaning of the digits in the > policy version, reads: > > | Thus only the first three components of the policy version are > | significant in the Standards-Version control field, and so either > | these three components or all four components may be specified. [5] > > > Now, I've only got the impressions that packages should avoid using the > 4th digit in their Standards-Version field, as that number has no > meaning when it comes to normative stuff. I've seen on IRC/MLs all kind > of comments saying that the 4th digit should be avoided, and most > packages avoid it indeed, but this wording in the policy makes me feel > like it's pretty much the same.
While I agree with you, what are the practical negative effect of putting the 4th digit in the Standards-Version field ? Lintian could easily be made to flag it, but is it worth the trouble ? Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.