>> I have to now recollect why I chose NOT to do that. There WAS a 'very >> valid' reason a couple of eves ago ...
> I am interested in your reason -- I would prefer to hack up that path rather > than risk breaking live installs. That, if I'm playing back my notes correctly, is exactly the reason I chose this route. I'm bundling up tarball'd installs for remote deploy (atm, using DIY scripts; eventually, Puppet etc). With $PREFIX 'hard-coded' on my dev/compile box, it's quite difficult to clobber an existing install by accidentally omitting DESTDIR= (either by my own doing, or that of a remote admin). In an env with fewer hands and just local keyboards, DESTDIR= is a fine option. ------------------------------------------------------------------------------ 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
