There is this sentence in the handbook now: "If you plan on using sysklogd or syslog-ng you might want to install logrotate afterwards as those system loggers don't provide any rotation mechanism for the log files." But there is very little information about installing logrotate, which is very often the choice. Users should be informed that in contrast to sysklogd or syslog-ng (which need to be rc-updated after emerging) there is nothing to must be configured in addition to "emerge logrotate", because there will be /etc/cron.daily/logrotate automatically created and used after emerging a cron daemon...
(In reply to comment #0) > But there is very little information about installing logrotate, > which is very often the choice. Users should be informed that > in contrast to sysklogd or syslog-ng (which need to be rc-updated > after emerging) there is nothing to must be configured in addition > to "emerge logrotate", because there will be /etc/cron.daily/logrotate > automatically created and used after emerging a cron daemon... Installation on Gentoo is pretty obvious: "emerge foo", in this case "emerge logrotate". And if there's no further configuration needed (since as you said, cron.daily is automatically created), then why should anything else be added to the documentation? The logrotate ebuild has some einfo after you emerge it that point you to its configuration file for any optional changes you may want to make. I use logrotate, and the only change I made was to move my portage logs to some special directory elsewhere. Otherwise, everything was handled automatically as you said. And if users are curious about what else it can do, well, the ebuild tells them where to find the config. :)
