Denis Solovyov wrote:
> 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.In the spec-file in the SRPM for instance. > Actually I thought that swup also used something like md5 checksums to > prevent changed files (even executables) from being upgraded... Why? What would that give you other than a hefty CPU load when upgrading? When creating the RPMs the creator marks the config files as such and hence they will not be touched during an upgrade. Any file not a config file should be overwritten to ensure a healthy system. New config files will have .rpmnew appended to their filenames so you can review them an merge the new and old file if you wish. If you have made changes to other files than the config files you should make your own RPM and tell SWUP to ignore that package. This puts the burden of keeping the package up-to-date on you, though. SWUP is a dependency handler mostly. RPM is rather helpless without it as it will just spew out dependencies and not solve them. And if you lose config files during upgrades it's because of a faulty package which you should file a bug report on. So if you state your specific problem we might be able to help you better :) -- *popping a Kilkenny and cheers*
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
