On Apr 24, 2021, at 23:23, Ken Cunningham wrote:
> On Apr 24, 2021, at 7:36 PM, Ryan Schmidt wrote:
>
>> Does only the first non-sudo `port` command fail? Does running the command
>> with `sudo` once allow it to work without `sudo` a second time?
>>
>> (There could be a one-time need to modify the registry sqlite database for
>> the new method.)
>
> Yes, indeed that seems to be the case. I just tried it again on that same
> system, and indeed I no longer need to use sudo for basic commands. Good
> catch.
Ok, then this is probably just the way it is for now. I seem to recall a
similar situation happening with some previous MacPorts base update. Whenever
we change the structure of the registry in some way, we increase the registry
version and there is code (our update_db function) that knows what SQL
statements need to run to convert an old registry version into the new one.
This requires write access to the database.
Maybe there is a way that we could postpone the sqlite update process until you
run a sudo port command. But depending on what the modifications are that the
update performs, a new MacPorts might not be able to understand the structure
of an old MacPorts registry until the sqlite update is performed.
