On Wed, Jul 17, 2013 at 12:10:35PM -0400, Bill Nottingham wrote:
I think it's more correct for packages that expect to work on a textual /var/log/messages (or similar) to have a requirement on a meta 'syslog' package (which all three major daemons provide), even if it's implicitly depending on the default configuration of those packages, rather than the alternative of *no* dependencies that we have now.
Sounds good, but:
$ repoquery --whatprovides syslog syslog-ng-0:3.4.1-1.fc19.x86_64 sysklogd-0:1.5-13.fc19.x86_64 rsyslog-0:7.2.6-1.fc19.x86_64 systemd-0:204-9.fc19.x86_64
$ rpm -q --changelog systemd|grep -B1 'Provide syslog' * Tue Oct 23 2012 Lennart Poettering lpoetter@redhat.com - 195-2 - Provide syslog because the journal is fine as a syslog implementation
Lennart, maybe this should be re-thought as to what "syslog" means exactly in this context? It's true that from an application-logging-stuff point of view systemd-jourald provides this, but maybe that's not right.
On the other hand, it looks like _only_ perl-Unix-Syslog has this as an explicit requirement, and that wants it for the logging capability, not for mucking with log output.