<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Apr 4, 2014 at 10:26 AM, Daniel J. Luke <span dir="ltr"><<a href="mailto:dluke@geeklair.net" target="_blank">dluke@geeklair.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Apr 4, 2014, at 10:00 AM, Brandon Allbery <<a href="mailto:allbery.b@gmail.com">allbery.b@gmail.com</a>> wrote:<br>
> 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. :(<br>
<br>
</div>We should mostly get out of the business of the perl p5 ports (or as much as possible).<br>
<br>
- offer one perl5 (the most recent stable release, currently 5.18.2)<br>
- make a glue layer that lets ports depend on modules, but has something like a custom cpanm actually do the install<br>
- maybe also have some 'rebuild all modules' magic that we can have the perl5 do when it gets upgraded<br>
<br>
... but so far, not many other people agree with me on this ;-)<br></blockquote><div><br></div><div>I can think of problems with that proposal. There aren't any good solutions, sadly. </div></div><div><br></div>-- <br>
<div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>