I see this message on every update: LOG: postinst If you don't have a makewhatis cronjob, then you should update the whatis database yourself: # makewhatis -u But, in most common scenario, a cron job is provided by man: /etc/cron.daily/makewhatis Then, I think that would be better to show the message if that file is missing as, otherwise, there is no need to manually run makewhatis -u Thanks Reproducible: Always
the counter point is that existence of a cronjob file does not mean you have a crond installed & running ...
But that case would apply to every ebuild providing a cron file and, then, following that reasoning we should add similar warnings for them also but, as we already have a specific section in Gentoo Handbook telling people to install a cron handled (vixie, dcron, cronie...), I think this kind of messages are not needed or, at least, we could reword handbook a bit to enforce more cron daemon installation
(In reply to comment #2) not all cronjobs affect the general operation of the program. it is not obvious that running `man -f` or `whatis` won't work without having the cronjob active.
If you want to be sure crond is started, maybe it could be checked with: if [ "$(rc-config list default | grep cronie)" = "" ] ; then elog "Blabla" fi The problem is that very cron implementarion uses a different name for his init.d file :S
(In reply to comment #4) yes, that and you can do ROOT= installs i've just thrown the message away. if people don't setup a cron daemon, then they can probably handle basic stuff like this.
Commit message: Drop whatis warning as most people will be using a crond http://sources.gentoo.org/sys-apps/man-pages/man-pages-3.43.ebuild?r1=1.1&r2=1.2
