On Fri, Jul 20, 2012 at 07:21:02AM -0700, Tom Eastep wrote: > > I think that this boils down to an issue with the Debian freeze period. > Were it not for the preference of the Debian release team to only accept > uploads that actually correct problems, we would all agree that it is > less confusing for users to have a matched set of components. > I agree.
> 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. > I am not sure this would be worth the extra trouble. I think that this may result in yet more confusion as well when you consider that there would be patches floating around out there with the exact same version numbers as the Debian packages, but with differences (e.g., the absence of the debian/ directory in your upstream tarballs). > 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). > I don't think this would help at all. It would simply result in the Debian packages being versioned as a.b.c-d-n (which while technically being a valid Debian version number, just looks funny to me). Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ 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
