On Thu, 17 Apr 2014 13:15:57 +0100, Stroller wrote: > On Thu, 17 April 2014, at 9:49 am, Neil Bothwick <n...@digimed.co.uk> > wrote: > >> ... > >> So I guess my question is: is this a bug with the app-admin/mcelog > >> package? > > > > I don't think so. If the running via cron is possible but deprecated, > > proving a cron script with execute permissions disabled seems a > > sensible way of covering both options. > > If this is the cause I would assume that everybody would be seeing the > same error message.
That assumes that everybody has mcelog installed, they don't. It doesn't even seem certain that this script is causing the problem. Apart fro whether or not the cron script is actually run, upstream considers running via cron deprecated, not broken, so including a cron script is perfectly valid for now. > I'm pretty sure a cron USE flag is in use elsewhere, I think it would > be better to have an option to install the package without the cron > script, rather than having to delete it manually each time one upgrades > the package. That's a fair point, except you don't have to delete anything. If the execute permission is not set, the script does not run. > USE=-cron will persist throughout updates, if it's set in make.conf or > package.use. It may be worth filing a bug requesting the use of that flag. -- Neil Bothwick If it ain't broke, break it and charge for repair.
signature.asc
Description: PGP signature
