[116204] trunk/dports/net/libproxy/Portfile

[David Evans]

On 1/21/14 10:56 AM, Ryan Schmidt wrote:
> On Jan 21, 2014, at 11:35, devans at macports.org wrote:
>
>> Revision
>> 116204
>> Author
>> devans at macports.org
>> Date
>> 2014-01-21 09:35:08 -0800 (Tue, 21 Jan 2014)
>> Log Message
>>
>> libproxy: depend on and build perl module for installed/default perl5.
>> Modified: trunk/dports/net/libproxy/Portfile (116203 => 116204)
>> -                    port:perl5.12
>> +                    port:perl5
> That’s exactly what we don’t want, isn’t it? We want predictable repeatable builds, not builds that vary based on other ports the user might have installed, but this change makes the libproxy port’s build vary based on what variant of the perl5 port is installed.
>
>
>
The intent is to build using the perl5 that is installed or if not
installed the default variant.  Isn't that reasonable? Why potentially
install an additional perl version in addition to what is already
installed if the port doesn't require it?

There's some inconsistency with the definition of perl5 and the perl
ports that are installed by its variants.  perl5's variants imply that
only one perl5 +variant can be installed at a time and that the user can
decide which one he wants and that's mostly true, but, in fact, other
perl5 versions can be installed that are different that the current
variant.  This can be helpful where the port actually requires a
specific perl version for one reason or another.

If you go by your reasoning, port perl5 should never be used as a
dependency, in which case, I'm not sure why it exists. Should all ports
that depend on perl5 be changed to depend on a specific versioned perl
port (presumably the default perl version) although they would work just
as well with another version? 

Just asking ;-)