On Sun, 17 Sep 2023 at 02:03:52 +0200, Santiago Vila wrote:
> If the files are intended to be modified "in place" by the
> system admin, we call them configuration files (and we try hard
> to put them in /etc). If they are not intended to be modified by
> the system admin, we don't call them
On Sun, Sep 17, 2023 at 12:12:18AM +0200, Daniel Gröber wrote:
> Sam, Russ, Bill,
>
> Thanks for your input. To be quite frank I still don't see how the
> interpretation of allowing configuration files outside of /etc can be
> supported based on the policy text.
>
> Ultimately I'm just concerned
El 17/9/23 a las 0:12, Daniel Gröber escribió:
Sam, Russ, Bill,
Thanks for your input. To be quite frank I still don't see how the
interpretation of allowing configuration files outside of /etc can be
supported based on the policy text.
Hello. I apologize for not having read the discussion in
Daniel Gröber writes:
> Ultimately I'm just concerned about the UX aspects of admins suddenly
> having to go hunting for config files all over their system when
> packages start implementing this config-in-/usr business en mass.
I think the expectation is that you read the documentation of the
Sam, Russ, Bill,
Thanks for your input. To be quite frank I still don't see how the
interpretation of allowing configuration files outside of /etc can be
supported based on the policy text.
Ultimately I'm just concerned about the UX aspects of admins suddenly
having to go hunting for config
On Thu, Sep 14, 2023 at 04:01:05PM +0200, Daniel Gröber wrote:
> Hello debian-policy,
>
> iproute2 has moved it's config files that were traditionally at
> /etc/iproute2 to /usr/lib/iproute2 due to an upstream change. I've tried to
> convince the maintainer(s) that this is a bad idea in
Daniel Gröber writes:
>> Any configuration files created or used by your package must reside
>> in /etc.
> Pretty clear cut in my reading, however this was promptly shot down by
> Bastian with the justification:
Configuration file has a very specific meaning in Policy: it's a file that
the
> "Daniel" == Daniel Gröber writes:
>> Any configuration files created or used by your package must
>> reside in /etc.
It's fine for packages to store defaults outside of /etc. But that 's
only true if you can override those defaults by placing a file in /etc.
8 matches
Mail list logo