Am Mittwoch, 8. Juni 2011, um 18:53:16 schrieb davidMbrooke:
> On Sun, 2011-06-05 at 22:09 +0200, KP Kirchdoerfer wrote:
> > Hello;
> > 
> > 
> > in the beginning the shorewall configuration files had an exhaustive
> > documentation including examples.
> > 
> > Later the documentation has been removed to improve support
> > size-constrained distros like LEAF, and was only available online or in
> > the man-pages (which we never added to our packages).
> > 
> > With the latest upstream version 4.4.20 the documentation has been
> > reintroduced into the config files, though the shrinked config files are
> > still around (using the -p option during install, or for our buildtoool
> > setup to package *.plain).
> > 
> > Beginning with Bering-uClibc 4.x we do not support a floppy-only setup
> > any longer and size can weighted up convenience.
> > 
> > My question is, do we want to include again the documented config files,
> > or shall we stick with the shrinked versions and pointing to the online
> > docs at shorewall.net?
> > 
> > kp
> 
> Hi kp,
> 
> I have just looked at the "annotated" config files in the Shorewall
> 4.4.20 distribution and IMHO the documentation will just get in the way
> when editing the files. My /etc/shorewall/rules file is already large
> enough :-)
> 
> My vote is therefore to stay as we are, using the "plain" files, and to
> clearly direct users to the online documentation at shorewall.net,
> though I am happy to be outvoted if others disagree.

Hi David;

you're not alone complaining about the changes, in the meantime Tom changed 
the default in 4.4.20.1, so in the latest packages I commited yesterday 
everything is as it was (at least it should be). :)

Anyway, *I* always liked the well-documented configuration files in the early 
releases (2.x), but get used myself to read the manpages instead.

sorry for the noise.

kp

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to