On 2015-11-18 09:44, René J.V. Bertin wrote: > On Tuesday November 17 2015 18:56:39 Ryan Schmidt wrote: > >> "port list" is a read-only operation; there's no reason why it would need to >> set a lock nor be restricted by a lock. > > And AFAIK so is everything that does not involve `port install`, `port > uninstall`, `port activate` and `port deactivate`.
The registry lock needs to be taken when the action relies on the set of installed ports. For example, when a 'port build' is running, you should not be able to uninstall a dependency at the same time. This could also be solved by very fine-grained locks on a per-port level, but the current approach of just locking the whole registry is less error-prone. Rainer _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
