Loading...
Request History
jsmeix created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
dimstar_suse set openSUSE:Factory:Staging:D as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:D"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:D"
dimstar accepted review
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:D got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:D got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:D got accepted.
No %config in /usr
%config %{_distconfdir}
Why can files in /usr not be marked as RPM %config files? Usually config files are in /etc but that is not my point. My point is why '%config /usr/...' is forbidden? Is there an openSUSE packaging URL that forbids it?
/usris completely package owned, admins must not write into it.Yes, I understand that admins should not modify vendor config files in /usr but admins are 'root' so they can do it and they are allowed to do whatever they like with their systems (they own their systems - not we). When admins modify "our" config files in /usr then %config could help them and us (e.g. SUSE support could see that "our" config files in /usr had been modified).
files in /usr WILL be overwritten by the package manager without exception. iff the admin does not want that, his config file (or fork thereof) MUST be in /etc.
1) Admins MUST NOT overwrite /usr ever: this is documented in most places
2) The actual issue was that having the files in /etc meant that the admin's copy and SUSE's copy existed in the same location which %config (or %config(noreplace)) is used to tell RPM how to handle this case and which file should actually exist at the specific filename. This usage is intentionally being changed so that SUSE's copy exists at /usr ALWAYS and is never modified and that admins as before will write to /etc and their changes aren't overwritten and co-exist with ours at the same time.
3) A package re-install / update would delete the changes so if a user did modify the /usr file and then asked SUSE Support - why did an update delete my modifications? - it's pretty clear they are editing the wrong file..
Being able to do something doesn't make it correct
Callum F (not employed by SUSE but have completed a lot of these changes)
Thank you for your explanation of the reasoning behind. Your request 1042360 is accepted and forwarded to openSUSE:Factory / cups as request 1042546.
I made a mistake regarding "SUSE support could see that 'our' config files in /usr had been modified": There is no need for %config for that because "rpm -V package_name" shows what files were modified.