On Jul 1, 2013, at 11:00 PM, Ryan Schmidt <[email protected]> wrote:
>>> and also ensure using the active_variants portgroup that the variant
>>> selected in each port is the same as the variant used in the intltool port?
>>
>> Again, why would that be?
>
> Because all ports using intltool are already required to add this line:
>
> INTLTOOL_PERL=${prefix}/bin/perl5.12
Gah... That is stupid. Why was this hackery propagated so far. The real fix
should be fixing that stupid autoconf macro and autoreconf-ing those ports.
>>> It was much more straightforward when the intltool port (and any other port
>>> that uses perl or perl modules) simply used perl 5.12.
>>
>> Yes, straight forward so long as you used +perl5_12. If you used a
>> non-default perl, you were out of luck.
>
> It should have worked, provided each port correctly specified that it wanted
> to use perl5.12. Granted there are many ports that do not correctly do this
> at present.
Well it didn't … and I'd rather fix it correctly than hack around the problem
in other ports.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
