Hi, On Wed, 28 Sep 2011 07:07:23 -0700 Tom Eastep <[email protected]> wrote:
> I'm frankly not interested in having to document and support different > flavors of configuration representation. I would be willing to include > hooks in the compiler for doing the conversion and for matching up > filenames and line numbers in the error messages to where an error or > warning occurred in the original source text, but I would prefer that > these alternate configuration formats be separate products that are > documented, maintained and supported by their creators. Actually, I'd like to go one step further and suggest to not bring this extra overhead into the project. It is a clear example of putting the cart in front of the horse. A better idea is that someone who needs this would write up some separate program that can take whatever input, XML or otherwise, and can export it to what shorewall currently supports. So to put it in bug tracker terms, I'd mark this as INVALID WONTFIX and I think it's safe to say that the majority of people who replied to the original idea agrees. There is nothing wrong with admins who write up their own wrappers which customise methods that are in use by the distribution or application. I, for one, replaced all of our networking init scripts with suitable alternatives that we control and are not rewritten or deleted when a package or distribution undergoes upgrades. - Mark
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
