Slaven Rezic <[EMAIL PROTECTED]> writes:
> DAGOLDEN <[EMAIL PROTECTED]> writes:
>
> > On 29 Nov 2007 20:20:29 +0100, Slaven Rezic <[EMAIL PROTECTED]> wrote:
> > > Is a workaround possible? Maybe you could turn the contents of
> > > PERL5LIB into a series of -I switches for "make test"? Or create a
> > > file with a series of "use lib" statements, and this file is used by
> > > all test scripts?
> >
> > I thought that Test::Harness 3.0 does this automatically? I.e.
> > CPAN/CPANPLUS sets PERL5LIB, then Test::Harness converts that into -I
> > switches before executing each .t file.
>
> Is this safe? During my test runs, I easily get a PERL5LIB with some
> 100 or 200 build directories. Translating this into command line
> arguments would create a command line with 20000 bytes or so. This is
> OK on my system (freebsd has a maximum of 256K for the length of the
> command line), but maybe other systems have smaller limits? That said,
> there are sure also limits on the size of the environment.
>
> >
> > If you can get T::H 3.0 working, it might be worth a try.
> >
>
> Yes, I will try it.
>
Using T::H 3.03 did not help. But indeed I see the PERL5LIB to command
line translation code in TAP/Parser/Source/Perl.pm.
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
Berlin Perl Mongers - http://berlin.pm.org