On Thu 2019-12-05 11:38:09 +0000, Georg Faerber wrote:
> On 19-12-05 08:29:44, Jorge P. de Morais Neto wrote:
>> But the user might have changed ~NOTMUCH_CONFIG~. On my Debian
>> install it is "~/.config/notmuch/config" (XDG compliant).
>
> It's possible to specify multiple conditions, and join these via OR:
>
> ConditionPathExists=|~/.notmuch-config
> ConditionPathExists=|~/.config/notmuch/config

I think we want to use %h instead of ~, but i haven't done much testing
(see SPECIFIERS in systemd.unit).

As for the variations, i'm kind of of a mind that people who deviate
from the defaults should need to maintain their own deviance explicitly,
rather than trying to accomodate a non-default path in shipped config
files.  For example, "systemctl --user edit notmuch-compact.timer" helps
you drop in the appropriate override/modification.

for that matter, do we want ConditionPathExists to constrain the .timer
or the .service (or both)?

And, what if the config file exists but the database has never been
created?

I've always felt like it was a bit weird that "notmuch setup" would
write the config file without at least initializing the database (though
perhaps this falls back into my general config file vs. database
concerns)

        --dkg