Tom Eastep wrote: > Tom Eastep wrote: >> Tuomo Soini wrote: >> >>> Imho version numbers don't cost very much. >> With Shorewall, a new full version number is not cheap; it takes a couple of >> hours to produce and results in new versions of all of the tarballs and >> RPMs, even if only one product changed. >> >> I propose that beginning with 4.0.7 that I adopt the kernel's naming >> convention; X.Y.Z is the base release; patch tarballs (and RPMs) are >> X.Y.Z.1, X.Y.Z.2, ... > > The RPMs that I produce for SuSE, TurboLinux, etc. will still encode the > patch level in the release number. So the RPM corresponding to X.Y.Z.n will > be shorewall-xxx-X.Y.Z-n.noarch.rpm rather than > shorewall-xxx-X.Y.Z.n-1.noarch.rpm
One other issue to decide; the kernel patches are cumulative -- should Shorewall patches also be cumulative so that distributions only have to apply the latest patch against the base release? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
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
