Hi,
Usually, the Inline module creates a ./_Inline directory as its working
directory.
But many of the testers appear to be using something like
/home/david/.Inline as Inline's working directory. How does that come about
?
If I'm guessing correctly, it's causing the PDL-2.4.3_01 inlinepdlpp.t tests
to fail. For those tests to succeed, one relies on the Inline working
directory being devoid of a pre-exisiting config file. My guess is that
there's a pre-existing config file in the Inline working directory (ie
'/home/david/.Inline' in this example) - and it doesn't specify 'Pdlpp'.
Hence the sort of test error we see at (eg):
http://www.nntp.perl.org/group/perl.cpan.testers/2008/10/msg2467899.html .
If my diagnosis is correct, then the cure is either:
a) delete the existing config file in /home/david/.Inline before running the
inlinepdlpp.t tests, or;
b) use a different Inline working directory for the inlinepdlpp.t tests (one
that doesn't have an existing config file in it).
Can either of those options be implemented ?
Is there something that we (the authors) can do to control this ?
Note that a) will work because the deletion of the existing config file will
force Inline to write a new one when the test is run - and when it writes
that new file it will detect that the Pdlpp support exists, and it will
specify Pdlpp (along with any other supported languages) in that new config
file .... and all will be fine.
But if there's a pre-existing config file in the Inline working directory,
it gets used as is ... and if it doesn't already specify Pdlpp (which it
won't), then we'll see the precise error message we're seing at the above
link.
Cheers,
Rob
