mmcintos@sirius.UVic.CA (Mark McIntosh) (04/24/91)
Std. Disclaimer: I haven't looked at Perl source much before, so don't
laugh too loud!
I would like to be able to enter multiple private libraries in
config.h (PRIVLIB) for Perl 4.0. I'd like to do this so that I can
have Perl install its "official" stuff in one and put local libraries
in another. At upgrade time, I can then define a new private library
directory (eg. .../lib/perl-4.0@3) where the "official" Perl stuff
can go and the other local libraries remain in another private library
directory. I could then do something like support Perl at different
revision levels on the same machine, without duplicating local library
files compatible with both. Clear as mud? Good.
I see that the in perl.c, non-tainted Perl reads the environment
variable PERLLIB and breaks it into multiple directories separated by
some path separator. Directly below that point in the code, I'd like
to apply that algorithm to the #define of PRIVLIB from config.h. Does
anyone see a problem with that? Is this truly useful?
I know this can be handled at runtime in various ways, but I would
like it compiled in. I read this newsgroup regularly, but if you
would prefer to reply by mail I will summarize if interest is shown.
Thanks,
Mark J. McIntosh <mmcintos@sirius.UVic.CA>
____________________________________________________________________________
University of Victoria, Faculty of Engineering - Dean's Office
Box 3055, Victoria, BC, CANADA \ "...the mystery of life isn't a problem to
V8W 3P6 (604) 721-6049 \ solve but a reality to experience."
UUCP: ...!{uw-beaver,ubc-vision}!uvicctr!sirius!mmcintos \ from Dunelwall@jpl-devvax.jpl.nasa.gov (Larry Wall) (04/25/91)
In article <MMCINTOS.91Apr23173231@sombrio.UVic.CA> mmcintos@sirius.UVic.CA (Mark McIntosh) writes:
: Std. Disclaimer: I haven't looked at Perl source much before, so don't
: laugh too loud!
That's okay, some of us have looked at it too much...
: I would like to be able to enter multiple private libraries in
: config.h (PRIVLIB) for Perl 4.0. I'd like to do this so that I can
: have Perl install its "official" stuff in one and put local libraries
: in another. At upgrade time, I can then define a new private library
: directory (eg. .../lib/perl-4.0@3) where the "official" Perl stuff
: can go and the other local libraries remain in another private library
: directory. I could then do something like support Perl at different
: revision levels on the same machine, without duplicating local library
: files compatible with both. Clear as mud? Good.
:
: I see that the in perl.c, non-tainted Perl reads the environment
: variable PERLLIB and breaks it into multiple directories separated by
: some path separator. Directly below that point in the code, I'd like
: to apply that algorithm to the #define of PRIVLIB from config.h. Does
: anyone see a problem with that? Is this truly useful?
:
: I know this can be handled at runtime in various ways, but I would
: like it compiled in. I read this newsgroup regularly, but if you
: would prefer to reply by mail I will summarize if interest is shown.
Sounds like a good idea to me, though there may be some programs that
assume @INC is a particular size or order--they shouldn't, of course.
Larry