Hi,
I noticed (= became annoyingly aware of the fact) that `port upgrade` does a
deactivate on the current port version before it even starts creating the
archive. Symptoms: while waiting for `port -nvk upgrade --force qt4-mac` to
finish, I got failure messages for starting kio_slave; that's because I'm
running kmail, which spawns regular short-lived helper applications that of
course link to Qt4. These arrived while my terminal showed the archive tarball
being created.
>From what I understand, upgrade (and install) do the following after the
>destroot step, disregarding the deactivating step(s):
- create a tarball in /opt/local/var/macports/software/portname
- unpack that tarball in a temp. directory in that same
/opt/local/var/macports/software/portname
- move items in place from the temp. directory into ${prefix}
If correct, it seems that deactivation of the currently active port version
could be done *after* filling the temp directory, to minimise the time the
system spends without the port installed.
This may not be very relevant for most ports, but ports like Qt4 and Qt5 are
both *huge* and can be quite central to user experience (using KDevelop or Qt
Creator for development, it could even be that one's IDE starts having issues
during the upgrade).
Thoughts?
René.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
