Hi folks,
thanks René, for reporting, but ...
On 27 Oct 2016, at 21:59 , René J.V. Bertin wrote:
> On Thursday October 27 2016 14:55:59 Ryan Schmidt wrote:
>
>>> That's what I told Marko too, but we're not talking here about the initial
>>> installation. I think that when
On Thursday October 27 2016 14:55:59 Ryan Schmidt wrote:
> > 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
> >
> On Oct 27, 2016, at 1:28 PM, René J.V. Bertin 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
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
wrote:
> On Thursday October 27 2016 11:12:10
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
Hi René,
The purpose of the active_variants portgroup is to provide error messages
like the one you mentioned, after checking whether a certain variant was
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
Hi,
Marko tells me he's been having issues with upgrading one of my KF5 ports that
uses the active_variants portgroup to "depend" on variants of one of its
dependencies.
From our exchange:
> > >> BUT that’s not all yet. Once also needs to select the +contrib variant,
> > >> otherwise you have