On Sat, Oct 4, 2014, at 04:46 PM, Roberto C. Sánchez wrote: > I've packaged the Debian versions of shorewall-lite and shorewall6-lite > to only depend on iptables, iproute, and bc. You should not even need > shorewall-core.
That's a different prereq setup, then, than my current sample set of both openSUSE pkgs, and DIY'd tarballs. Consistent prereqs/dependencies across upstream tarball builds & distros seems like a good idea -- but, certainly haven't thought through the distro-specific issues. My current upstream tarball install of -lite appears to require -core, rm -rf /usr/local/shorewall-custom cd ./shorewall-lite-4.6.4-Beta2-34-ge36b34c/ sh -x ./install.sh shorewallrc.suse ... + echo 'Installing Suse-specific configuration...' Installing Suse-specific configuration... + '[' -z /usr/local/shorewall-custom/etc/init.d ']' + '[' -n '' ']' + '[' '!' -f /usr/local/shorewall-custom/share/shorewall/coreversion ']' + echo 'shorewall-lite 4.6.4-Beta2-34-ge36b34c requires Shorewall Core which does not appear to be installed' shorewall-lite 4.6.4-Beta2-34-ge36b34c requires Shorewall Core which does not appear to be installed + exit 1 Need to look closer to see what/why the dependency actually is. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users