Re: avoiding conflicts with %config

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/3/05, Will Harris <will.harris@xxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am not sure if this is possible, but I am trying to find a way to
make a custom package with a set of (edited) config files and security
changes. However since these config files belong to other packages (ssh,
xinetd, selinux, etc) I get conflicts. I can force it, but then
upgrading the package becomes another hassle.
I'm wondering if there is some macro I am missing that will let me
install my config but not cause the conflicts for the original package
on update. I would not mind if I even had to reinstall my custom
package. Does anyone know of any trick to accomplish this?
 
I don't know if this will suite your tastes or not, but what I do is deliver the config
files to some alternate location and then in the %post scriptlet overwrite the originals with these files.   Seems to work fine, and even plays well the rpm transactional rollback feature.  
 
Cheers...james

 
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux