Question about profile.d scripts definition in Spec file

Michael Schwendt mschwendt at gmail.com
Wed Aug 5 11:23:00 UTC 2015


On Wed, 05 Aug 2015 06:37:41 -0400, Colin Walters wrote:

> On Tue, Aug 4, 2015, at 01:38 PM, Michael Schwendt wrote:
> >
> > Either %config or %config(noreplace) can cause problems during update.
> > Neither one is completely safe with regard to breaking a program at
> > runtime. It can be necessary to switch from %config(noreplace) to %config,
> > or vice versa, in updates.
> 
> FWIW rpm-ostree (really ostree) consistently uses the equivalent of
> %config(noreplace) always for everything in /etc, regardless of what the
> input RPM says.
> 
> I think global predictability and consistency here is superior to
> per-package choice.

MUST: Admin must painstakingly review and handle all .rpmnew/.rpmsave files,
which are created when installing an update.

Aiming for consistency, I agree with that. Predictability? Nah. Both %config
and %config(noreplace) bear risks.


More information about the devel mailing list