On 10/3/2014 8:11 AM, PGNd wrote:
> 
> 
> On Fri, Oct 3, 2014, at 07:36 AM, Tom Eastep wrote:
>> As I pointed out yesterday, when you use 'DESTDIR', the installation
>> created is *not runnable*. DESTDIR is the means by which packagers are
>> able to do their work - it creates an installation that is effectively
>> rooted in $DESTDIR. When installed by the various package systems into
>> /, it works correctly.
> 
> Then a misunderstanding on my part.  I've been consistently pointing out my 
> interest/intent in a runable install -- from within, and contained to, a 
> 'sandbox'.
> 
> In that context, DESTDIR= was still discussed as a better option, or so I 
> understood.
> 
> Reverting to my prior install method using the hard-coded, $PREFIX'd 
> "bizarre" shorewallrc config ...
> 

I've just pushed a patch that implements a -n option in the installers
(with the exception of Shorewall-core), which inhibits any attempt to
allow the product to start at boot time.

-Tom
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
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

Reply via email to