Re: Finding old library directories (was Re: automatic perl module rpm wrapper)

[Tim Bunce <Tim.Bunce@ig.co.uk>]

On Sun, Jan 09, 2000 at 03:51:05PM +0000, Nick Ing-Simmons wrote:
> Gurusamy Sarathy <gsar@ActiveState.com> writes:
> >
> >2. If the answer for #1 is 'y', Configure should look for directories like
> >m{(\Q$installprefix\E/lib(/perl5)?/site_perl/(5.\d{3,5}|\d+\.\d+\.\d+))/auto/}
> >on the filesystem, and add $1 and $1/archname to the default list
> >of directories, if they exist.  (The site library layout actually changed
> >in some versions of perl, so additional patterns may need to be looked for.
> >Andy knows that history best.)
> >
> >I don't see why hardwiring anything is necessary.  Am I missing some
> >desired functionality in the above?
> 
> Well some of us use a different installprefix, but that is only 
> to stop accidental use of wrong lib directories.
> 
> One could go hunting for executable perls a then do 
> 
> /path/to/a/perl -e 'print join("\n",@INC),"\n"'

Why hunt for other perls? If you've used a different installprefix to
put a perl into a non-standard place and "to stop accidental use of
wrong lib directories", surely such perl's should be left alone.

"hunting for executable perls" just seems wrong.

Tim.

---

Follow-Ups from:

Nick Ing-Simmons <nik@tiuk.ti.com>
Andy Dougherty <doughera@lafayette.edu>

References to:

Gurusamy Sarathy <gsar@activestate.com>
Nick Ing-Simmons <nick@ing-simmons.net>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---