1. app-admin/msyslog, sys-apps/sysklogd, app-admin/syslog-ng and app-admin/metalog don't PROVIDE anything (like "virtual/logger"). They really should so that they can block each other (RDEPEND="!virtual/logger"). 2. sysklogd really belongs to app-admin, I think. Or move the other 3 loggers into sys-apps. I'm not quite sure...
Moving sysklogd probably makes sense. It's just in sys-apps due to long-standing inertia. The lack of a "provide logger" in the system logger ebuilds suggests that we don't have any packages in portage that have logger dependencies. Since I suspect that we have at least one log analyzer in portage, that fact surprises me. So yes, "provide logger" should probably be added. I do disagree that the various system loggers should block each other. My view is that packages should only block if installing one package clobbers part of another (which is definitely true in the case of the various mtas, for example, as each provides a /usr/sbin/sendmail). I _know_ the loggers can coexist just fine, at least in the case of sysklogd and metalog. It is true that users should not run more than one logger at a time, but that's a different issue.
thilo's on holiday, so handing to you grant, if that's ok...
Waiting for drobbins new move-packages support in Portage.
Moved. I hope!
