On 23 July 2012 04:31, Togan Muftuoglu <[email protected]> wrote: > On 07/20/2012 04:21 PM, Tom Eastep wrote: >> >> Regarding your second approach above, I notice that Debian (and most >> other distros) add a "-n" to my version number. So my 4.5.5.3 is >> released as 4.5.5.3-1. So presumably, users would not be confused if >> they saw shorewall-core-4.5.5.3-1 and shorewall-4.5.5.3-2? If I were to >> release individual patches along with the consolidated patch for each >> product, would that help (I would only need to do that during the freeze >> period). You could then apply those patches that did not bump the >> version number and upload the patched product as -2, -3, etc. It would >> be more work for the two of us during the freeze period but would spare >> everyone else. > > -n for opensuse build process means the build number > >> >> An alternative would be for me to change my release numbering system >> from a.b.c[.d] to a.b.c-d, but I suspect that move would cause >> disruption to all of the distro maintainers (and some amount of work for >> me). > > Please do not do that change as opensuse build service barks to releases > with -d (d being anything) in it. I would vote that you keep the > numbering as it is
Yes, this is also the case with Fedora (and presumably any other RPM based distros); the "-" is used as the separator for the upstream version and the package release number. Hence the upstream version can't have a "-" in it. If shorewall were to add one, we'd have to work around that in our packaging by eg replacing the "-" with a "_" or something. Do-able, but a Royal PITA. J ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
