qtcurve update failure

[René J.V. Bertin]

On Tuesday December 13 2016 11:22:09 Mojca Miklavec wrote:

>So:
>- you have an old qtcurve installed
>- the new qtcurve will have a new runtime dependency qtcurve-extra
>- qtcurve-extra doesn't depend on qtcurve, but fails to activate if
>qtcurve is already installed?
>
>Or did I misunderstand something?

No, that's correct.

>
>From what I understand this is exactly the case where you would want
>to use the deactivate hack. You would expect users to run
[..]

Yes, indeed. The only question I have is how the upgrade process handles variants. Suppose the user has the old qtcurve installed with +qtonly. Will that variant be preserved when the actual qtcurve upgrade starts, even if qtcurve is deactivated and regardless of how many versions/variants are installed? Even if it does it'll still be a bit brittle in case anything unforeseen goes wrong during the qtcurve-extra install.

It'd be a bit complicated to test this on my end now.

And supposing this is issue is moot, should I still add the hack, or can we do as Marko suggested?

R.