On Sat, Oct 4, 2014, at 07:11 PM, Tom Eastep wrote: > Please remember that the installers were never designed to install a > runnable sandbox. This is just another case where the installer is > assuming that the directory exists if DESTDIR isn't set -- it now > creates the directory.
I do remember. Yet, a runable shorewall install in a sandbox is still my goal. I certainly admit a frustration with the different approach to an installer _here_ than with other apps (e.g., your typical autofoo-based install), yet ACK that the choice was made for likely good reasons. And, I'll keep plugging away at this until I have a clean, well-behaved solution - whether integrated into upstream, or a local kludge. If the only eventually viable answer is to abandon upstream's build/install system, and instead build an rpm, ok; I've yet to come to that conclusion. Apart from the currently infrequent errant message, it seems to be eminently possible to install a runable sandbox. That said, the aforementioned FAIL notification, "ERROR: Failed to install -T -o root -g root -m 0544 init.suse.sh /usr/local/shorewall-custom/etc/init.d/shorewall-init" though perhaps accurate, doesn't do much to identify/suggest the solution -- namely, making sure the prerequisite -core is installed. Hence the suggestion to possibly check for the prereq, and fail gracefully with an informative notification, nothing more. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
