Christian Soeller wrote: > > On 9/11/2009, at 4:08 AM, Chris Marshall wrote: >> >> Also, be sure you don't have another copy of PDL in your @INC >> when you are running the tests as that can result in mysterious >> and highly confusing failures... > > > This is a really *glaring* weakness of the current testing environment > (which I have run foul of myself). Is PDL the only large installation > suffering from this? > How can one fix this? Are CPAN testers potentially affected?
The cleanest way might be to add a utility function to PDL::Core::Devel that would check the current @INC minus the just built PDL libraries for a needed module. It probably does not affect CPAN testers as much because they usually start from a clean environment and build from scratch most of the time. > If somebody were to work on improving stability and installability this > would have to be high on the agenda. It should be low hanging fruit. We should probably ask on the CPAN testers or perl modules list for suggestions as well. --Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
