On 13 December 2016 at 10:54, René J.V. Bertin wrote:
> On Tuesday December 13 2016 10:30:24 Mojca Miklavec wrote:
>
>>See:
>> https://trac.macports.org/wiki/PortfileRecipes#deactivatehack
>
> Ah, yes, I forgot about that link, though I did consider deactivating in the
> pre-activate phase. It'll be a bit trickier here because I'd be deactivating
> an older version of one of the ports that will be upgraded later, and I don't
> know what effect that will have on preserving the right variants.
>
> To explain:
> qtcurve-extra is a new run-time dependency for qtcurve, and will be installed
> (first) during `port upgrade qtcurve`.
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?
>From what I understand this is exactly the case where you would want
to use the deactivate hack. You would expect users to run
port upgrade outdated / port upgrade qtcurve
rather than starting with
port install qtcurve-extra
without upgrading the rest of the ports first. If other ports are
upgraded before attempting to manually install qtcurve-extra, there
should be no problem. If they are not ... well, I would blame the
user.
Mojca
