> 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. > > You may recall that I originally uploaded only changed packages but that > seemed to cause angst among the user population. > > Recent questions from the Debian release team about the current practice > have prompted me to revisit the issue. As I see it, there are three > possible approaches: > > 1) Continue to release all packages.
May I suggest to NOT change the system again, not the release system, not the install system nor the packaging options built into the Shorewall distribution! There are many more packagers than the Debian or Fedora folks. Maybe they don't speak out, but still have to reflect all the changes which have been done in the past in their kind of packages. And there were many changes in the last couple of months... I prefer if the Shorewall devs - of course mainly you Tom :) - do work on Shorewall itself. Thanks Tom, you are doing an excellent job! Regards, Simon ------------------------------------------------------------------------------ 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
