On Apr 14, 2007, at 22:41, Paul Guyot wrote:
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. }
Ok, that's what I'm doing (in sleepwatcher), but it's resulting in weirdness: "port info" shows two "universal" variants; see: $ port info sleepwatcher | head -n 1 sleepwatcher 2.0.4, Revision 2, sysutils/sleepwatcher (Variants: universal, server, universal) (This is with my ports tree indexed by portindex from macports trunk as of a few moments ago.)