Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 571012 - >app-admin/sysstat-11.0.2 - re-introduce cron use flag to control creation of /etc/cron.d/sysstat
Summary: >app-admin/sysstat-11.0.2 - re-introduce cron use flag to control creation of...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Jeroen Roovers (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-05 17:42 UTC by Hank Leininger
Modified: 2016-06-22 06:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Re-introduce a cron USE flag, default to on. (sysstat-11.2.0_ebuild_USE_cron.patch,946 bytes, patch)
2016-01-05 17:44 UTC, Hank Leininger
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Hank Leininger 2016-01-05 17:42:45 UTC
sysstat used to have a 'cron' USE flag to control whether /etc/cron.d/sysstat was created, but it went away at some point.  This is still documented in, for example, https://wiki.gentoo.org/wiki/Sysstat

I'll attach a simple patch that re-introduces a cron USE flag as +cron so that the default behavior after applying will be the same as before, but, gives the user the option to turn it off via portage.use.

This is related to, but not quite the same as this bug: https://bugs.gentoo.org/show_bug.cgi?id=531032

This change would be an effective workaround for that bug.

Reproducible: Always
Comment 1 Hank Leininger 2016-01-05 17:44:51 UTC
Created attachment 422036 [details, diff]
Re-introduce a cron USE flag, default to on.
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2016-02-05 06:37:18 UTC
We've been up and down this path since forever. Search for bugs about app-admin/sysstat needing to either install or not install cron files or the right type or make it optional. It is now truly well-trodden and I am hesitant to "fix" it again because it's bound to break it for others.

The ebuild uses the upstream defaults now and you can override those locally by setting CONFIG_PROTECT or INSTALL_MASK or a combination.