On Mon, Dec 10, 2007 at 10:13:54AM +1000, Paul Gear wrote: > Andrew Suffield wrote: > > On Sat, Dec 08, 2007 at 03:49:53PM +0000, Jonathan Underwood wrote: > >> No, I'm afraid that wouldn't address the issue. Fundamentally, it's > >> incorrect to use the package release number (after the hyphen) to > >> reflect a version number of the software being packaged (in this case > >> the patchlevel of the tarball). RPM is a bit inflexible in it's > >> approach to using a hyphen as the version-release separator, but none > >> the less, it's now a well established strategy. > > > > It's a historical inanity. For the record, dpkg simply considers the > > *last* hyphen in the version to be the separator, and you can include > > as many other hyphens as you like before that. > > You can say that all you like, but none of us have the ability to "fix" > this historical inanity in RPM on all the distros it's used on. > Well, we could all switch to .deb-based distros :-p
> Personally, i think if a fix is significant enough to be released, it > should have a different version number (e.g. 4.0.6.1 or 4.0.7, depending > on Tom's preference). > While that is certainly debatable, I think that catering to the lowest common denominator (for lack of a better term) is probably the best approach. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
