conflict between "portA +python33" and "portB +python33"
cal at macports.org
Mon Apr 7 14:42:53 PDT 2014
> All good in theory.
> In practice the port uses the cmake PortGroup which defines
> "pre-configure" step and it seems that it overwrites the one from
> active_variants, so adding
> require_active_variants portB "" +python33
> doesn't have any effect at all.
pre-configure blocks don't overwrite each other, they get queued up
(although the order may be undefined).
More information about the macports-dev