On 19/07/2012 15:31, Tom Eastep wrote: > It has been my practice for some time to always upload all of the > packages when one of them changes. This includes patch releases such as > 4.5.5.3. >
This is really an argument about whether to version individual components or the distribution as a whole... I just saw an almost identical question on the Perl blogs rss feed - can't remember which project it was for, but the question again was whether to mark the whole release of all packages with a version, or to version the individual components. Ahh, yes, just remembered, the sub issue was then how to put the version numbers into the individual modules so that lib-1.2.3 is known to be part of distribution-1.2.5 The majority opinion was that there are some thorny problems with having two part version numbers. I think the same also in your case here, it's not obvious to a package dependency system that shorewall-core-1.2.3 is acceptable for shorewall6-1.2.5. Gentoo would typically define the dependencies as simple variables that are constructed from the base package name you are installing, and so letting these versions get out of lockstep would be annoying and extra work (and likely lead to bugs) My thought would be that generally people on Debian are quite happy running shorewall 3.x despite shorewall-4.5 being out. Don't panic too much about their freeze, if users of Debian want to get bang up to date they can come upstream and get their packages... This is a distro management problem, not your problem Cheers Ed W ------------------------------------------------------------------------------ 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
