On 1/19/22 12:40, Petr Pisar wrote:
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.
Thank you. This statement about /var was indeed an attempt to justify
the change outside ostree-enabled systems. But as it seems to be false
and it created unexpected discussion I rephrased the section to:
"""
These files are used by authselect to detect changes to the system
nsswitch and PAM configurations when the configuration is updated with
an updated profile using 'authselect apply-changes'.
Unfortunately, the current location conflicts with ostree model where
/var is not writable during rpm transaction and this currently blocks
compose of ostree systems (see BZ#2034360). At the same time /usr is
read-only on client side of ostree-enabled installations therefore the
files can not be moved there since it would break authselect on the
client side.
Storing these files under /etc/authselect will make authselect work on
both server and client side of ostree systems.
"""
-- Petr
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
