On Fri, Apr 4, 2014 at 10:26 AM, Daniel J. Luke <[email protected]> wrote:
> On Apr 4, 2014, at 10:00 AM, Brandon Allbery <[email protected]> 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 [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
