On Tue, Jul 20, 2021 at 08:34:33PM +0000, Eric Wong wrote: > > Okay, let me see what I can come up with. Looks like the best course of > > action > > is to: > > > > 1. use a global blocking lock > > 2. copy the config file to a new location > > 3. make the necessary changes to the temporary config file > > 4. move the temp config file to overwrite the current config > > 5. release the lock > > public-inbox-init already does all of that. It doesn't set > all possible keys, yet (e.g. infourl, maybe some others).
I figured as much, but we do want to set extra keys *and* write the config in a certain order (e.g. prioritizing some sources over others by listing them first). I currently do this via a list-id globbing match (e.g. --listid-priority=*.linux.dev,*.kernel.org,*). Apropos, question -- will public-inbox-init do anything to the config file if it finds that all the settings are already in place, or will it just accept them? -K
