Is the `tmpfiles.d` drop-in actually necessary?
Description:
I was going through a rather minimal base system looking to do immutable A/B /usr/
updates and what would need to be done that this is possible (yes, I know that isn't officially supported). I noticed that this package seems to be one of the only ones I saw on that system that activly modify /usr/
post installation via it's tmpfiles.d
entry.
I did see in the git blame
for the line that this commit added the file but I am somewhat left wondering, how do other packages/distributions handle these kinda cases (or is this the only one)?
I did ask in the mkosi channel what the best way to addess this problem might be (or if it might really even be something worth worrying about) and they said that generally having things not owned by root in /usr/
is kinda broken and should be fixed, so I am unsure how to continue.
Generally this isn't a deal breaking issue, as mkosi runs sd-tmpfiles during its build, so the mode is correctly set (I think? Since only
/usr/
is shipped I am unsure that the actual GIDs persist, but probably are regenerated the same deterministically)