default_variants and variant conflicts
René J.V. Bertin
rjvbertin at gmail.com
Fri Oct 30 14:48:45 UTC 2020
I still have some recurrent problems with variants and causality/serialness.
I'm now developing a set of Python variants (mutually exclusive) for a port, declared and defined programmatically and with the latest python version as the default variant.
I don't really understand but can live with the fact that I need 1 first loop to declare the variants (with an inner loop to generate the appropriate conflicts list), then set the default variant and only then do another loop to check variant_isset and do the actual work.
But why doesn't `default_variant` notice that it's setting a variant that conflicts with a variant set by the user? That means I have to check variant_isset in my first loop too, just to determine whether or not the user set a variant...
More information about the macports-dev