Wolfgang Braun wrote:
On Fri, Feb 04, 2005 at 01:48:59PM -0800, Richard E. Perlotto II wrote:
And then you would have two logrotate files for many of the same files. This is a worse situation. Since syslog many times is considered a base OS package it cannot be removed.
It can be removed no problem if there's another package that provides 'syslog' (or sysklogd not sure). This could be done in the syslog-ng spec file.
The SRPM I submitted for QA in Fedora.us already has a Provides statement: "Provides: sysklogd = 0:1.4.1-99" Right now, the only problem I am having, is how to improve the handling of the syslog/syslog-ng logrotate file: it only works if there are no sysklogd upgrades (no problems if sysklogd is removed). As Enrico suggested in comment 23, a possible solution may reside in the usage of %trigger scripts. All possible solutions/comments are welcome (even better if they are submitted via bugzilla). References: * Fedora.us syslog-ng QA comments https://bugzilla.fedora.us/show_bug.cgi?id=1332 This package aims to be a replacement of RedHat/Fedora sysklogd (tries to follow the same logging rules). * Packaging software with RPM, Part 3 Running scripts at install and uninstall http://www-106.ibm.com/developerworks/library/l-rpm3.html Regards, jpo -- José Pedro Oliveira * mailto: jpo@di.uminho.pt * http://gsd.di.uminho.pt/~jpo * * gpg fingerprint = F9B6 8D87 859D 1C94 48F0 84C0 9749 9EB5 91BD 851B *