Re: Add Debian revision number standards to policy?
On Tue, 01 Nov 2005, Nathanael Nerode wrote: I was surprised to discover that the standard rules for Debian revision numbers (maintainer revisions contain no dots; source NMUs contain one dots; binary NMUs contain two) are not in Policy, but only in the Developer's Reference. They are not even where they need to be toolwise, binary NMUs break strict versioned dependencies hideously... Should a policy patch be created? IMHO, Yes. IMHO you should also add that you are only to use numbers without zero padding (not that the tools will break if you pad, AFAIK, but...), that they must increase monotonically, that NMUs start with 1 and binary NMUs start with 0.1 if there isn't a NMU version yet, or NMU.1 if there is one. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Add Debian revision number standards to policy?
On Thu, Nov 03, 2005 at 01:01:22AM -0200, Henrique de Moraes Holschuh wrote: On Tue, 01 Nov 2005, Nathanael Nerode wrote: I was surprised to discover that the standard rules for Debian revision numbers (maintainer revisions contain no dots; source NMUs contain one dots; binary NMUs contain two) are not in Policy, but only in the Developer's Reference. They are not even where they need to be toolwise, binary NMUs break strict versioned dependencies hideously... Should a policy patch be created? IMHO, Yes. IMHO you should also add that you are only to use numbers without zero padding (not that the tools will break if you pad, AFAIK, but...), that they must increase monotonically, that NMUs start with 1 and binary NMUs start with 0.1 if there isn't a NMU version yet, or NMU.1 if there is one. I presume you mean: they should go up by one each version. Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
