[MacPorts] #12710: perl5 portgroup should be able to write in
privlib dir for the bundled modules
MacPorts
trac at macosforge.org
Tue Jan 29 05:48:30 PST 2008
#12710: perl5 portgroup should be able to write in privlib dir for the bundled
modules
-------------------------------+--------------------------------------------
Reporter: nox at macports.org | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone: MacPorts base enhancements
Component: base | Version:
Resolution: | Keywords:
-------------------------------+--------------------------------------------
Comment (by vinc17 at macports.org):
Replying to [comment:14 nox at macports.org]:
> The installation of a custom p5-test-harness in #13745 is unneeded,
you're right. But it doesn't break anything.
It currently breaks upgrades if the -f option isn't used.
> If a core module file is omitted in your solution, we will need to force
installation again,
I suppose you mean an upgrade of the Perl core port.
> whereas a reversed @INC path avoids this shortcoming.
Yes, but there's a still problem for the binaries and man pages with this
solution. The only workaround I can see is that the user would need to
modify his $PATH environment variable in his shell rc file(s). But note
that if you regard this modification as acceptable, then the user could
also modify his $PERL5LIB environment variable at the same time, meaning
that the reversed @INC path is completely unnecessary.
> So if we create a new port for an updated core module, we'll have to
increase the revision of perl base port and to remove the files of the
core module from it. That's not elegant.
I don't think there's any elegant solution.
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/12710#comment:15>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list