[112798] trunk/dports/archivers/upx/Portfile

[Ryan Schmidt]

Well, this is the reason I haven’t touched it. It was convenient to have a port providing “perl”, “pod2man”, etc. The “port select” mechanism is what we decided we wanted to use, but that it was for a user’s convenience, and that ports cannot rely on a user having chosen any particular version. Lots of configure scripts and build systems will try to use “perl”, “pod2man”, etc. If we switch perl to use “port select” and get rid of the perl5 port’s symlinks to MacPorts versions of those, then those build systems will fall back to using the OS X versions of those programs. That might be fine. If not — if a program requires a newer perl — then the dependency can be updated and the build system patched.

On Nov 1, 2013, at 15:30, Jeremy Lavergne <jeremy at lavergne.gotdns.org> wrote:

> Knew I shouldn’t have bothered trying to make perl.  Reverting r112798 in r112809.
> 
> snark/
> Oh well, maybe the ticket can just sit for another two years.
> Or can we just remove perl, wholesale?
> /snark
> 
> On Nov 1, 2013, at 16:10, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
>> These dependencies are not correct: the perl5.12 port does not provide “perl”, “pod2man”, “pod2text”, or “pod2html”; it provides “perl5.12”, “pod2man-5.12”, “pod2text-5.12” and “pod2html-5.12”.
>