On Apr 15, 2007, at 12:32 PM, Ryan Schmidt wrote:
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?
No. You just define your own universal variant with:
variant universal {
# Your code goes here.
}
As a matter of fact, if you do:
variant universal {
# some code
}
universal_variant no
You'll end up having no universal variant in your portfile. But this
is an undocumented behavior.
Paul
_______________________________________________
macports-dev mailing list
[EMAIL PROTECTED]
http://lists.macosforge.org/mailman/listinfo/macports-dev
