On Mon, 06 Oct 2003 15:37:12 -0400, Geoffrey Young wrote
> > Should we try to squeeze it into 1.29? If so do we need another release
> > candidate? Since we need 1.29 out asap, because of the bug in 5.8.1, I
> > suggest that we release 1.29 as it is now. Then hopefully we will
> > release 1.30 some time soon (including the PERL5LIB fix). I know there
> > are quite a few patches that Philippe has planned to put in and we want
> > them to sit in the cvs for some time to get people time to test it out
> > well.
>
> my advice would be to get 1.29 out soon, as it will be the first
> stable version of mod_perl specifically for 5.8.1.
>
> release 1.30 can come with those patches, and be released at a much
> more leisurely pace
>
> --Geoff
I'm happy with that. There's also another problem with PERL5LIB that I've
noticed, but not fixed because there's an easy workaround:
According to perlrun(1), architechture subfolders are added to @INC as well:
PERL5LIB
A colon-separated list of directories in which to look for
Perl library files before looking in the standard library
and the current directory. Any architecture-specific
directories under the specified locations are automatically
included if they exist.
For example on my dev box, setting PERL5LIB to '/home/simonflk/perllib'
should add '/home/simonflk/perllib/i686-linux' if it exists.
The simple and obvious workaround is to add that to PERL5LIB. But it would be
nice for it to behave as documented in perl. If the other fix to PERL5LIB is
scheduled for v1.30, it makes sense to fix that for the same release. When I
get some time I'll send in a patch.
Thanks
--simonflk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
