<p dir="ltr">On May 15, 2015 5:15 AM, "Lawrence Velázquez" <<a href="mailto:larryv@macports.org">larryv@macports.org</a>> wrote:<br>
><br>
> On May 14, 2015, at 3:43 PM, David Evans <<a href="mailto:devans@macports.org">devans@macports.org</a>> wrote:<br>
><br>
> > I understand what you're saying, but this seems to me to be in the<br>
> > category of fixing things that aren't broken. In addition, it<br>
> > complicates maintenance by opening us up to perl version specific<br>
> > problems on the various platforms, particularly older ones.<br>
> ><br>
> > I would favor depending not on the system perl or perl5 but use the<br>
> > default perl (currently perl5.16). This is in line with our general<br>
> > perl guidelines and ensures consistent behavior on all platforms<br>
> > regardless of the system perl version.<br>
><br>
> I agree with this policy 99.9% of the time, but I think autoconf merits<br>
> an exemption:<br>
><br>
> - As the maintainer, I of course take responsibility for any issues that<br>
> arise. I have access to systems with Leopard through Yosemite and have<br>
> not seen any regressions or inconsistencies due to this change.<br>
> - I want devs to be able to add "use_autoconf" or "use_autoreconf" to<br>
> their ports if necessary without worrying about the relatively large<br>
> Perl dependency. I would like to liberate Automake also, but I haven't<br>
> looked into it yet.</p>
<p dir="ltr">This is a welcome improvement from my POV as a user and port maintainer. I certainly know a newbie or two who were put off from using MacPorts when they tried to install something seemingly trivial and that unexpectedly pulled in "half the world".</p>
<p dir="ltr">-- <br>
Arto Bendiken | @bendiken | <a href="http://ar.to">http://ar.to</a><br>
</p>