On Mar 14, 2021, at 07:51, René J.V. Bertin wrote: > Supposing runtime dependencies are stored in the registry,
Yes of course. > wouldn't it be possible and a good idea to give at least a warning if any are > missing when you (re)activate a port? It shouldn't warn; it should install or activate any deps that are missing. It looks like MacPorts is trying to do that already, but there appears to be a bug: $ port deps paracode Full Name: paracode @2.8_1 Runtime Dependencies: python39 $ sudo port -f deact python39 paracode ---> Deactivating paracode @2.8_1 ---> Cleaning paracode ---> Unable to deactivate python39 @3.9.2_1+universal, the following ports depend on it: [snip] Warning: Deactivate forced. Proceeding despite dependencies. ---> Deactivating python39 @3.9.2_1+universal ---> Cleaning python39 $ sudo port act paracode ---> Computing dependencies for paracode ---> Dependencies to be installed: python39 Error: Failed to activate python39: Registry error: python39 @2.8_1 is not installed. Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_macports-ports-ryandesign-fork_lang_python39/python39/main.log for details. Warning: Failed to execute portfile from registry for paracode @2.8_1 ---> Activating paracode @2.8_1