V Wed, Jan 19, 2022 at 11:55:48AM +0100, Pavel Březina napsal(a):
On 1/19/22 11:35, Petr Pisar wrote:
> V Wed, Jan 19, 2022 at 11:30:11AM +0100, Pavel Březina napsal(a):
> > On 1/19/22 11:04, Petr Pisar wrote:
> > > V Tue, Jan 18, 2022 at 12:32:52PM -0500, Ben Cotton napsal(a):
> > > > Since /var should contain only files that can be safely removed,
> > >
> > > While I agree with your change, this statement is false. /var is for any
files
> > > which are variable. Files which can be safely removed belong to /var/tmp
and
> > > /var/cache.
> >
> > Though when removed, the application should remain functional and just
> > recreate it automatically, right?
> >
> Yes.
>
> > Authselect would require user intervention.
> >
> Yes.
Ok, how about phrasing it:
Removing these files would reduce authselect functionality, user would need
to run 'authselect select --force' to restore it. This however conflicts
with purpose of /var which should contain only data that do not affect
functionality when removed.
That's better, but still not right. /var is not about "functionality
when
removed". /var is simply about files which can change (as an opposite to
a change when installing a software). (Compare to
<
https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#purpose31>. E.g. if
you delete /var/spool/mail, then a lot of people will say that a functionallity
of their mailboxes is seriously affected.)
I would simply remove the sentence "This however...". Because the truth is
that the conflict is not with the purpose of /var.
If you want reason why /var is not suitable, then simpy admit that /var is
not managed by os-tree and that thus you need a better location which /etc
seems to be because you are moving authconfig's configuration files.
-- Petr