<div dir="ltr">I (and I think Daniel Luke) just want to abolish all but the latest Perl. We allow the installing of perls that have LONG since gone out of updates. Perl goes out of its way to be backwards compatable. You have to do things like "use 5.16" to even use new features that break stuff.<div>
<br></div><div>Mark</div></div><div class="gmail_extra"><br clear="all"><div>—Mark<br>_______________________<br>Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank">emer@emer.net</a>><br></div>
<br><br><div class="gmail_quote">On Tue, Jun 10, 2014 at 7:34 PM, MacPorts <span dir="ltr"><<a href="mailto:noreply@macports.org" target="_blank">noreply@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">#43480: perl: remove subrelease number from lib path<br>
</div><div class="">-------------------------------------------------+-------------------------<br>
Reporter: mojca@… | Owner: macports-<br>
Type: enhancement | tickets@…<br>
Priority: Normal | Status: new<br>
Component: ports | Milestone:<br>
Resolution: | Version:<br>
Port: perl5.8 perl5.10 perl5.12 perl5.14 | Keywords:<br>
perl5.16 perl5.18 |<br>
-------------------------------------------------+-------------------------<br>
<br>
</div>Comment (by mojca@…):<br>
<br>
I still agree that we probably want to talk to the developers, but I went<br>
ahead and applied a patch r120890 to `perl5.20`. Given that the port is<br>
completely new anyway, we won't break anyone's functionality and if the<br>
idea turns out not to work ... well then we can revert it.<br>
<br>
The problem with upstream is that they have a different model of<br>
installing and using Perl than MacPorts does and I understand why for them<br>
the model works and why they wouldn't want to switch to what I did, at<br>
least not by default. One installs one version of perl and keeps it there<br>
even after installing the next new version. But MacPorts removes the old<br>
version (and doesn't provide experimental versions) and there's where the<br>
problems start.<br>
<br>
We need to make a strong case and request a new feature, so that they<br>
would add a new configure option.<br>
<br>
I would suggest to apply the same change also to `perl5.18`. (Or maybe<br>
we'll change the way Perl works altogether anyway.)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Ticket URL: <<a href="https://trac.macports.org/ticket/43480#comment:2" target="_blank">https://trac.macports.org/ticket/43480#comment:2</a>><br>
</font></span><div class="HOEnZb"><div class="h5">MacPorts <<a href="http://www.macports.org/" target="_blank">http://www.macports.org/</a>><br>
Ports system for OS X<br>
</div></div></blockquote></div><br></div>