location of libperl.dylib and other dylibs

Brandon Allbery allbery.b at gmail.com
Fri Apr 4 08:05:40 PDT 2014

On Fri, Apr 4, 2014 at 10:26 AM, Daniel J. Luke <dluke at geeklair.net> wrote:

> On Apr 4, 2014, at 10:00 AM, Brandon Allbery <allbery.b at gmail.com> wrote:
> > People are still trying to figure out how to deal with perl ports; there
> was a recent aborted attempt at building a port select mechanism for it
> instead of that perl5 metaport with variants, which ran into lots of
> problems. The whole thing is annoyingly tricky to deal with, and the
> solutions don't appear to be simple. :(
> We should mostly get out of the business of the perl p5 ports (or as much
> as possible).
> - offer one perl5 (the most recent stable release, currently 5.18.2)
> - make a glue layer that lets ports depend on modules, but has something
> like a custom cpanm actually do the install
> - maybe also have some 'rebuild all modules' magic that we can have the
> perl5 do when it gets upgraded
> ... but so far, not many other people agree with me on this ;-)

I can think of problems with that proposal. There aren't any good
solutions, sadly.

brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140404/5d9033fd/attachment.html>

More information about the macports-dev mailing list