I try to sum up what I think that should be done with this issue.
Name is unresolved. I chose "mutable" as an interim one.
%mutable will be defined for REG files and LINKs.
Behavior :
- if a file/link is the same as in new package
(it has the same contents, gid, uid and mode)/(is
Thinking about it some more... what we're actually talking about here is a file
update policy. An update policy is a selection of operations such as whether to
replace modied files or not, to backup or not etc. When looking at it from this
perspective, it all starts making more sense: %config is
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
%confi
Add
* update by patching
and make the policies platform and machine specific.
Then call the implementation something catchier than ansible or DevOps.
Seriously: configuration != package management.
--
You are receiving this because you commented.
Reply to this email directly or view it on Git
In order to build chroots using Mock on armhfp hosts for armsfp targets, rpm
needs to allow installing packages for armsfp architectures on an armhfp host.
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1440974
You can view, comment on, or merge this pull request online at:
https://git
OK this actually seems to work quiet well for the SSD case - you're
fdatasync()ing every 32kB which is nice.
We'd not want it on by default - any place with a non-ssd is going to go poorly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
