Hi, I would like to use errata/patches to update both shorewall and shorewall-lite. Are files such as lib.cli "always" going to be the same in shorewall and shorewall-lite? In this case applying current patch #2 to both shorewall and shorewall-lite makes sense. However, "automating" patching would result in an "error" applying patch #4 to shorewall-lite since lib.tunnels doesn''t exist there. Furthermore, according to errata/Shorewall-lite, it seems that "modules" should be patched with patch #1 in shorewall only (but I think it can be patched to -lite too?). I think it might help to distinguish patches by their filename or directory, eg.: patch-3.4.1-1.diff (applies to both) patch-3.4.1-2.diff (applies to both) patch-shorewall-3.4.1-4.diff (applies to shorewall only) likewise: patch-shorewall-lite-3.4.1-4.diff (applies to shorewall-lite only) I think this would make automation easier/clearer. Or maybe I''m missing something and I''m getting it all wrong. Please correct me. Vieri ____________________________________________________________________________________ We won''t tell. Get more on shows you hate to love (and love to hate): Yahoo! TV''s Guilty Pleasures list. http://tv.yahoo.com/collections/265 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
On Fri, Mar 23, 2007 at 08:22:00PM -0700, Vieri Di Paola wrote:> I would like to use errata/patches to update both > shorewall and shorewall-lite. > Are files such as lib.cli "always" going to be the > same in shorewall and shorewall-lite? In this case > applying current patch #2 to both shorewall and > shorewall-lite makes sense. > However, "automating" patching would result in an > "error" applying patch #4 to shorewall-lite since > lib.tunnels doesn''t exist there.Why bother? It''s not like there''s a long time between releases, especially when there are known issues with the last one. You might as well just wait for the next release to come out, and base any deployments on the tarballs. It should be quite rare that you actually need to grab something from the errata directory - most of the time it''s just corner cases or obscure features. If there''s anything really important in there, Tom usually gets a new point release out shortly afterwards. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV