rpm install conflicts

[Tapan Kamat <rpm_guy yahoo com>]

Hello everybody

I have a few doubts about the way rpm functions. I
already have an older version of apache installed and
am installing a newer one. I know that using the
upgrade "U" switch will install the package without
any probs. But what I need to know is how rpm
understands the conflict examples of which are
presented below :

file /etc/httpd/conf/httpd.conf from install of
apache-1.3.27-1.7.2 conflicts with file from package
apache-1.3.23-11

file /usr/lib/apache/mod_actions.so from install of
apache-1.3.27-1.7.2 conflicts with file from package
apache-1.3.23-11

I feel that since the first file httpd.conf is a
config file (specified under %config), rpm can detect
the modification. But why is it that mod_actions.so 
modification (overwriting) is detected as well ?

In general, I have observed that whenever you install
a rpm package, it will overwrite all files, except the
config files,without even warning the user. Why is
there an exception in this case? Pls. note that this
is just one example. Actually, I am getting atleast 20
more filename conflicts as above for even non-config
files.

Thanks
Tapan Kamat




__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com