Am Dienstag, 30. Januar 2007 08:59 schrieb Christian Gmeiner: > Hi all..
Hi Christian, > At the moment we have the following situation: > > User selected to strip all shorewall files in /etc/shorewall and > /usr/share/shorewall and he wants the default installed configfile set > in /usr/share/shorewall/configfiles. > > After a make all files in /usr/share/shorewall are stripped, but all > files in /usr/share/shorewall/configfiles not. Should dir configfiles > also striped? If so, i can commit a modified version of downstrip > script, which runs recursive over all dirs. The shorewall configfiles normaly consists of a lot comments about the syntax used for configuring zones,interfaces,nat,masq,rules, etc..This comments can really be a great help for users that are configuring shorewall (and even I have to look up stuff in the comments a lot) I believe it's enough to give the user the chance to have the original configfiles installed in /etc/shorewall, so that he can lookup the correct syntax directly in the config file that the user wants to edit. If the user decides, that he doesn't need the comments at all, then he can install a striped down version in /etc/shorewall. If the user isn't a shorewall expert, then he can lookup the comments on the shorewall website or on another machine running shorewall. I don't see any sense in shipping this stuff also in /usr/share/shorewall/configfiles, espacially because almost nobody will find it there and it is only needing disk space. If you strip these configfiles, they are useless anyways, because then you have almost empty files without any help for the user. So my wish is to NOT ship them, and if you really want to ship them, then please DON'T strip them. regards, Ralph _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
