%config causing file conflict error

[jupiter]

Thanks Greg. Please embedded comments.

On 8/25/12, Greg Swift <gregswift at gmail.com> wrote:
> As far as i am aware there is no disabling that.

So there is not tag in rpm spec to have the same function of forcing
installation (force replacement) without using --force? I thought if
you can do something in rpm command line, it should have the same
functional tag in spec, very much like to use "Autoreqprov: no,
Autoprov: no, Autoreq: no" for --nodeps, right?

> I see what you are doing,  but can you explain why? Maybe we can give a
> better answer knowing more.

As I said, I have two applications sharing the same configuration file
(There is a reason for doing it, let's not try to change it). If none
of the application package is installed, the first one instals the
configuration file, then the second application package should do
nothing if it finds the configuration file has already been there.
Although the "%config config.txt" is used in spec, I really don't mind
if the configuration file is overwritten or not as long as it is
there.

The problem I've got is that rpm failed to install the second
application package as an error of conflict. Although I can use rpm
--force to force the installation, I really want to know if there is a
spec tag I can use to stop rpm installation checking the conflict, or
just force it override the config file.

Thank you.

Kind regards,

Jupiter