[Swan-dev] should test /etc/ipsec.conf files be stand-alone

[Paul Wouters]

Making them stand alone will cause important parts to get out of sync.

We have thought about completely
removing the includes so that the test cases act as documentation files but didn't decide on doing it.

So for now I'm afraid you'll have to tar up
/testing/baseconfigs/

Sent from my iPhone

> On Oct 20, 2015, at 20:31, Andrew Cagney <andrew.cagney at gmail.com> wrote:
> 
> Hi,
> 
> I just noticed that, for tests, the /etc/ipsec.conf file isn't exactly
> standalone.  For instance, for the test ikev2-04-basic-x509,
> /etc/ipsec.conf ends with the include:
> 
>    include    /testing/baseconfigs/all/etc/ipsec.d/ipsec.conf.common
> 
> which creates problems, for instance:
> 
> - I'd really like to be able to grab the entire config and run it else where:
>   ssh west 'cd / ; tar cf - etc/ipsec.d etc/ipsec.conf' | ssh red 'cd
> / ; tar xpf -'
> 
> - hard-wiring /testing to a single source tree prevents me from having
> multiple build/test directories.
> 
> thoughts,
> Andrew
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev