nested port upgrading and variants

[David Strubbe]

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.

On Thu, Oct 27, 2016 at 11:28 AM, René J.V. Bertin <rjvbertin at gmail.com>
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.
>
> R.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20161027/7d885e53/attachment-0001.html>