ryandesign at macports.org
Sat Apr 14 20:32:31 PDT 2007
On Apr 14, 2007, at 22:04, Paul Guyot wrote:
> On Apr 15, 2007, at 11:53 AM, Ryan Schmidt wrote:
>> On Apr 13, 2007, at 22:34, source_changes at macosforge.org wrote:
>>> Modified: trunk/base/doc/portfile.7 (23967 => 23968)
>>> --- trunk/base/doc/portfile.7 2007-04-14 01:54:40 UTC (rev 23967)
>>> +++ trunk/base/doc/portfile.7 2007-04-14 03:34:33 UTC (rev 23968)
>>> @@ -1331,6 +1331,26 @@
>>> .Sy Example:
>>> .Dl default_variants +ssl +tcpd
>>> +.It Ic unversal_variant
>>> +When using MacPorts on MacOS X, a universal variant is defined and
>>> +the default behavior is to configure ports with universal flags
>> Wait... I thought the default behavior was for the +universal
>> variant to be available to all ports, but that you had to select
>> it if you wanted to use it.
> This is what I meant, or at least tried to express. +universal will
> be available to all ports unless they specify "universal_variant
> no". And universal variant code will have no effect (except listing
> this variant as available) unless users select +universal. The
> default behavior *of the universal variant* is to configure with
> universal flags.
> Please feel free to correct the wording to make the man page easier
> to understand.
I see what you meant now. :)
So, these changes you're making... are they the solution to the
problem I reported when I want to define my own universal variant?
Should I be (as soon as released MacPorts supports it) using
"universal_variant no" before defining my own universal variant?
More information about the macports-dev