Tom Eastep wrote: > > All this having been said, I haven't yet started using the LrpN project > again since 2.2.0 as I haven't officially opened a 2.3 development > release. Also, I don't maintain the LrpN/ project in sync with the > /Shorewall2 project on a daily basis so if you need that project > updated, please let me know. >
Sorry for following up my own post but I hit the <send> button too quickly. One of the problems with the current Shorewall CVS is that the changes that are unique to the .lrp are not maintained as patches that can be applied to my released code. The Lrp*/ projects in my CVS are simply images of the .lrp which means that when I change a file like shorewall.conf that has an lrp-specific version then I have to manually apply the change to the appropriate Lrp*/ project. I have long wanted to rework that so that the .lrp could be built from the mainline CVS project (as the .rpm is) with the lrp-specific content and patches being the only thing kept in CVS. It would make my job a lot easier and would make it possible for Leaf folks to build a .lrp from my latest development code without me having to manually apply changes. Any volunteers? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
