[Swan-dev] tests referring to source

Andrew Cagney andrew.cagney at gmail.com
Fri Mar 11 15:06:40 UTC 2016

On 10 March 2016 at 10:53, Paul Wouters <paul at nohats.ca> wrote:
> If I can run make in /testing/lib/libswan that would work for me, but it only compiled if in /source. I would have preferred to stay in pluto-basic-00 because now I had to hack around to get the rest for prompt :)

Can I please have the real Paul back? :-)

For basic-pluto-00, how about:

- run the previously installed
- enumcheck and algparse just print to stdout
- the existing console diff logic can check that the output didn't
change, or if it did what happened


- no magic make
- no cat

Since cavs is installed in libexec, I argue prior art :-)

I need to think about newoe-20-ipv6

> Sent from my iPhone
>> On Mar 10, 2016, at 15:44, Andrew Cagney <andrew.cagney at gmail.com> wrote:
>> I've noticed a few of the tests playing around in the /source
>> directory (the latest example is basic-pluto-00 but it isn't the first
>> :-).    I'd like to avoid this.  I think it would be better to have
>> tests stick to either the local directory's files; or stuff previously
>> installed (even if it is with a special test-install target).
>> Beyond my immediate problem of not having a standard /source, this
>> "dogma" (only test what you install) should help us long term:
>> - test binaries are built up-front, and, hence, are more likely to be maintained
>> - packagers can bundle the test binaries opening the possibility of
>> running libreswan's testsuite against a packaged install
>> Andrew
>> _______________________________________________
>> Swan-dev mailing list
>> Swan-dev at lists.libreswan.org
>> https://lists.libreswan.org/mailman/listinfo/swan-dev

More information about the Swan-dev mailing list