[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59423: Invalid 'location' field generated in dovecot configuration
From: |
Ludovic Courtès |
Subject: |
bug#59423: Invalid 'location' field generated in dovecot configuration |
Date: |
Fri, 02 Dec 2022 22:18:41 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Ludovic Courtès <ludo@gnu.org> skribis:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
[...]
>> No :-). I meant why do we even set a default accessor for the *source
>> location* information (in the (gnu service configuration) macros); it's
>> that one that doesn't seem to get used (or I'm blind to it!), at least
>> via this accessor. If it's not strictly necessary, we can stop
>> producing it, and that would solve the problem.
>
> Like I wrote, I think it’s necessary, even if not used now.
To complement this answer: key high-level record types usually have a
‘location’ field: <package>, <channel>, <mapped-device>, <file-system>,
<service-type>, etc. The rationale is that it allows us to report
accurate location info for errors and warnings, to jump to their
definition, and so on.
For configuration records this is not a common pattern, but the
rationale holds. ‘zabbix-front-end-config’ uses the ‘%location’ field,
but it seems to be the only one so far.
Ludo’.