<div dir="ltr">I agree with you about what should happen. I just wanted to clarify that the active_variants portgroup doesn't make that happen, and probably cannot -- this is a base issue.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 27, 2016 at 11:28 AM, René J.V. Bertin <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thursday October 27 2016 11:12:10 David Strubbe wrote:<br>
<br>
Hi David,<br>
<span class=""><br>
<br>
>used for a dependency. That's all it does. The only way I know of that you<br>
>could make opencv get installed with +qt5 in this context is to do "port<br>
>install kf5-digikam-devel +qt5" (whether that is a meaningful variant for<br>
>kf5-digikam-devel or not).<br>
<br>
</span>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.<br>
<span class="HOEnZb"><font color="#888888"><br>
R.<br>
</font></span></blockquote></div><br></div>