On Fri, Oct 12, 2007 at 09:16:47AM -0700, Tom Eastep wrote: > I'm unfamiliar with the current Debian release schedule but I'd like to > encourage you to do everything you can to ensure that there is a Shorewall 4 > package available in the next major Debian release.
The last one was in April, and they're usually 18-24 months apart (the current rough goal is October 2008, but these rough goals are routinely missed by months). Not an issue. > Otherwise, we'll to be > in the same old boat where when the new Debian stable release comes out, it > is already a major Shorewall release behind the upstream. I think shorewall would be a suitable candidate for uploading into volatile-sloppy, which lets users install individual updated packages on stable systems. That should eliminate this issue, for both the current release and future ones. (Other well-known packages which are handled by the volatile system include spamassassin and clamav; shorewall would get filed under 'sloppy' because upgrades across releases require administrative attention to changes in the config files, so should not be performed automatically) Basically, a user would run a pure Debian-stable system on their firewall, with the single exception of the shorewall package. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
