Discussion:
[PATCH] no archlib in otherlibdirs
(too old to reply)
Rafael Garcia-Suarez
2008-02-25 11:49:28 UTC
Permalink
Don't include archlib into otherlibdirs automatically.
This should be added explicitly and is most of the time not wanted.
However, otherlibdirs is documented to be searched for
architecture-specific directories. I'm not sure what your use case is.

Your patch also includes moving the priority of SITELIB for older
versions above the VENDORLIB for the current version. That can be
debated too.

(I keep promising to post a plan for 5.12, but one of the items is
already listed in perltodo:
=head2 Modernize the order of directories in @INC
Having better use case descriptions can only help here.)
Andy Dougherty
2008-02-29 17:59:17 UTC
Permalink
Post by Rafael Garcia-Suarez
Your patch also includes moving the priority of SITELIB for older
versions above the VENDORLIB for the current version. That can be
debated too.
Our use case: The reason for this was, that I package with cygwin a
bundle of modules needed for cpan bootstrapping, like LWP and deps.
Otherwise the new user cannot install other modules.
As soon as an updated module version is being installed via cpan, this
should take over the default, older version from vendor_perl. If not
newer, it will not be installed via cpan. If newer, it will be installed
(if tested ok), AND should be used.
Yes. This is a reasonable scenario. I think this will work as intended
as long as there is only ever one version of perl installed at a time.
If there is more than one version installed (even transiently, for example
during an upgrade) then it is a bit more complex. For a more general
solution, see the link already listed in perltodo.
Post by Rafael Garcia-Suarez
(I keep promising to post a plan for 5.12, but one of the items is
--
Andy Dougherty ***@lafayette.edu
Loading...