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. 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). -- Paul <http://paul.gear.dyndns.org> -- Did you know? Linux is a completely free operating system that provides a vast array of software "out of the box", and represents a viable alternative to expensive proprietary software. For more details, see: http://consumer.hardocp.com/article.html?art=MTI5OCwxLCxoY29uc3VtZXI=
signature.asc
Description: OpenPGP 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
