I'm packaging some of my own software, as part of the installation I need to drop some config files in a directory that's used by a 3. party.
To avoid overwriting configuration that have been locally changed, that file is marked as a config file like so in the RPM .spec file:
%config(norelace) /opt/lmd/conf/srv1.conf
The issue is that upgrading an rpm will now produce the file
/opt/lmd/conf/srv1.conf.rpmnew
if /opt/lmd/conf/srv1.conf have been altered locally. And the 3.d party software reads everything in /opt/lmd/conf/* .
Can I somehow mark a config file in the RPM .spec file to not produce such an .rpmnew file ?