>> Is it OK that swup upgrades "touched" config files (for example, in
>> /etc) along with executables?
MS> Usually, but, as always, important data and configs should always be
MS> backed up, just in case.
Well... it is not always possible to understand immediately that
something was overwriten (especially is swup is started from cron).
>> Please explain how swup decides to overwrite or not overwrite an
>> existing file.
MS> This is actually handled by RPM. The install of a package should have
MS> configuration files specified and the file should be written only if
MS> there is not an existing file. For instance, this is from an apache RPM:
MS> %config(noreplace) %{_sysconfdir}/httpd/conf/httpd.conf
Hmm... where exactly in RPM are such "rules" situated? Can't find
anyone.
Actually I thought that swup also used something like md5 checksums to
prevent changed files (even executables) from being upgraded...
Denis Solovyov
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss
