Am 05.06.20 um 23:31 schrieb Kenneth Porter:
--On Friday, June 05, 2020 1:39 PM -0700 John Pierce
<jhn.pierce@xxxxxxxxx> wrote:
don't most packages create a .rpmnew file if you've modified the previous
package file ?
That file is created AFTER you've made edits, and reflects only the
state of the file in the latest package. So it's not clear what changed
from the original package that needs to be migrated into one's current
settings.
As a rule I try to copy the original files to xxx.original so I can
compare that to both the .rpmnew file and my working file. But I or
another admin might forget to save the original. So I end up going the
cpio route to extract the original files to a temp tree to do the 3-way
comparison between the original, my modifications, and the latest
package's modifications.
Your needs are very specific. So, I think you need to write a custom
script for that.
What we do here is, packaging the custom configuration files (rpm).
The source package (srpm) has also the original or distribution
version of the configuration file. Downloading the current original file
in a pre task and patching it while building the rpm helps us to track
the changes ...
--
Leon
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
