changing default perl
emer at emer.net
Mon Nov 4 16:05:11 PST 2013
I'm with you there. 5.8 and 5.10 are long out of support. The Perl
community also strongly advises moving to the latest version as soon as it
is marked stable, that's why they make you do things like: use 5.018; to
get new features that can break old ones. Which is why I'm leaning more and
more toward nuking all but the latest perl and away from port select.
Mark E. Anderson <emer at emer.net>
On Mon, Nov 4, 2013 at 9:44 AM, Daniel J. Luke <dluke at geeklair.net> wrote:
> On Nov 3, 2013, at 4:42 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> > On Nov 3, 2013, at 15:38, Mark Anderson wrote:
> >> Although we do need to come up with a better perl strategy. The current
> workings drive me crazy.
> > I’m curious why that is. We use this strategy for PHP and Python as well
> and IMHO it works very well there. Do those drive you crazy also, or is it
> just Perl, and if so, what makes Perl different?
> php/python versions exists because there are substantial changes in the
> language(s) that things written against the older versions not work with
> newer interpreters.
> For perl5 that is largely not the case (there are things that have
> changed, but mostly in backwards-compatible ways).
> perl is also a little different in the wide number of things available on
> CPAN, and the tendency of (many? most?) people working with perl to make
> use of CPAN modules whenever possible.
> I'm not aware of a compelling use-case for keeping many versions of perl5
> around (or at least one that makes sense in the context of MacPorts) -
> while it does make things more complicated for our end-users.
> Daniel J. Luke
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> | Opinions expressed are mine and do not necessarily |
> | reflect the opinions of my employer. |
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users