(Jun 25 2005 04:25) Denis Solovyov wrote: > > Is it OK that swup upgrades "touched" config files (for example, in > /etc) along with executables?
SWUP does not touch any _files_, it only installs, removes and upgrades _packages_. The package is the one that touches config files. And to answer your question: Yes, it both OK and perfectly sane behaviour. > Please explain how swup decides to overwrite or not overwrite an > existing file. RPM desides by doing the following: If the installed package tells us a file is a config file, rpm checks the md5sum stored in the database against the md5sum of the file on the filesystem. If the md5sum is the same, the content is the same, and the file is overwritten. If the md5sum is not the same, RPM checks the database to see if the installed package marks the file as 'noreplace'. If a file is marked as such, the file is left alone, and the file in the new package is stored as filename.rpmnew . If the file is not marked as 'noreplace' it's moved to filename.rpmold and the new file is stored as filename. So as you can see it's up to the package developer to decide what files are config files and how they are tagged. If, however, you do _change_ a config file so that the content is different, and that file is overwritten when the rpm is upgraded, you should file a bug report. Hope this helped. c -- Christian H. Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
