registry lock

Jeremy Lavergne jeremy at
Tue Nov 17 10:48:00 PST 2015

I believe the inquiry surrounds why we trigger a lock for the duration of
all phases when doing an install. Specifically, why do we not instead set
the lock only when in phases that could changes installed files.

So abstract a bit further beyond just uninstall phase: why do we need to
lock anything when we're not yet changing installed files?

On Tue, November 17, 2015 13:36, Joshua Root wrote:
>> I may have asked before, so apologies if I forgot the answer:
>> Why does "base" need a registry lock for operations up to destroot? I
>> realise configure and beyond may require installing missing ports, but
>> that could lead to locking the registry only when those ports are to be
>> installed. When none are missing a lock shouldn't be required, right?
> What if you uninstall some ports in another terminal while the operation
> is running?

More information about the macports-dev mailing list