nested port upgrading and variants

Ryan Schmidt ryandesign at
Thu Oct 27 12:55:59 PDT 2016

> On Oct 27, 2016, at 1:28 PM, René J.V. Bertin <rjvbertin at> wrote:
> On Thursday October 27 2016 11:12:10 David Strubbe wrote:
> Hi David,
>> used for a dependency. That's all it does. The only way I know of that you
>> could make opencv get installed with +qt5 in this context is to do "port
>> install kf5-digikam-devel +qt5" (whether that is a meaningful variant for
>> kf5-digikam-devel or not).
> That's what I told Marko too, but we're not talking here about the initial installation. I think that when you already have opencv+qt5+opencv installed, an automatic upgrade to opencv should behave like `port upgrade opencv`. IOW, it should maintain the active variants. Anything else is a waste of time and source of frustration.

I'm not aware of any reason why that wouldn't happen. MacPorts preserves variants on upgrades.

More information about the macports-dev mailing list