Hi,

Why does a pre-activate phase happen before a deactivation phase when upgrading 
from an older port revision to a newer one?

I would have expected the following order:
  ...
  pre-deactivate v1
  deactivate v1
  post-deactivate v1
  ...
  pre-activate v2
  activate v2
  post-activate v2

But MacPorts (2.3.3) uses the following order:
  ...
  pre-activate v2
  pre-deactivate v1
  deactivate v1
  post-deactivate v1
  ...
  activate v2
  post-activate v2

Kind regards.

Artur
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to