It is pretty annoying for any package to install a cronjob without asking the user for input or the admin to specifically enable it.
(In reply to comment #0) > It is pretty annoying for any package to install a cronjob without asking the > user for input or the admin to specifically enable it. You want to discuss this on g-dev?
(In reply to comment #1) > (In reply to comment #0) > > It is pretty annoying for any package to install a cronjob without asking the > > user for input or the admin to specifically enable it. > > You want to discuss this on g-dev? > Not really. QA policy has just masked a package for removal because it wrote cron configuration (among other reasons) and net-analyzer/munin has an emerge --config step to install its crontab too. Those are just a few examples off the top of my head.
(In reply to comment #2) > (In reply to comment #1) > > (In reply to comment #0) > > > It is pretty annoying for any package to install a cronjob without asking the > > > user for input or the admin to specifically enable it. > > > > You want to discuss this on g-dev? > > > > Not really. QA policy has just masked a package for removal because it wrote > cron configuration (among other reasons) app-admin/webmin, I guess. It does not install a cron.daily file like man2html: | »···# Bug #194305 | »···addpredict /var/spool/cron/crontabs > and net-analyzer/munin has an emerge > --config step to install its crontab too. Those are just a few examples off the > top of my head. And if you grep the tree for packages installing to cron.(hourly|daily|weekly|monthly) you will find many ebuilds installing a cronjob without asking for userinput.
(In reply to comment #4) > And if you grep the tree for packages installing to > cron.(hourly|daily|weekly|monthly) you will find many ebuilds installing a > cronjob without asking for userinput. > yup, closing bug