On Tue, Oct 16, 2007 at 12:28:23PM +0200, Holger Levsen wrote: > Hi, > > On Sunday 14 October 2007 19:00, Roberto C. Sanchez wrote: > > * Package name : shorewall4-lite > > First of all, why do you propose shorewall4 packages instead of just > upgrading > shorewall to version 4? > I have already closed this ITP. I am simply going to setupa migration to version 4 of shorewall based on the current packages.
> > Description : Shoreline Firewall, Netfilter configurator (lite > > version) > > The shorewall4-lite package is designed to allow you to maintain all > > Shorewall configuration information on a single system within your > > network. > > I dont see whats special or lite about this, this is just the way shorewall > works :-) > Basically, You only need one system with a full shorewall install. This machine can then generate a script that can be executed on a machine with shorewall-lite. Thus, you can install the full shorewall on a test/development server and then shorewall-lite on the production machines, or something like that. > But thats probably related to my questions about shorewall4-perl and -shell: > their proposed long description ends with: "This version of Shorewall > includes > a compiler written in perl|shell." - does that mean, that shorewall is a > general purpose compiler now? Wow! ;) Please enhance the description to > describe what kind of compiler that is and what its used for. > It already says that it is for configuring netfilter. I'm not certain how much clearer I can make it. I copy/pasted from the current package descriptions, which have been fine for quite a while. > Also those two packages claim their programming language is "sh" - I wonder > if > this is right... (maybe it is, and the compiler written in sh compiles perl > or shell code... and compiles it to iptables code?!) > The sh for the -perl package was a mistake. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
