Just to enumerate what sort of things an update policy would consist of, from
the top of my head:
- whether to install the file in the first place (default obviously yes, but
%ghost does not get installed at all)
- whether to replace files (default being yes, currently only changable with
%config(noreplace))
- whether to backup overwritten files (default being no, %config enables)
- whether file metadata should be updated (default yes, no for %ghost and some
other arguably buggy cases, and then one might actually want metadata updates
for %ghost files)
...and probably something else too, but that's what rpm currently implements in
the typical ad-hoc manner. So here's a fine chance to make things less ad-hoc
as well.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/152#issuecomment-293539537
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
