On 15/03/13 11:51 AM, Adam Williamson wrote:
On 15/03/13 08:30 AM, Miloslav Trmač wrote:
On Fri, Mar 15, 2013 at 4:11 PM, Daniel P. Berrange
<berra...@redhat.com> wrote:
Users shouldn't have to go searching out that kind of thing in a
separate package IMHO, it could just be part of stock yum install.
If it needs to be optional a config param would suffice, rather
than the big hammer of installing/uninstalling extra RPM to enable/
disable a feature.

Yeah, we don't generally do configuration by package
installation/uninstallation.

In this case it seems perfectly logical. The thing in question is a cron
script. You want it, install it. You don't want it, don't install it.
How would this be implemented with a config parameter in a way which
wouldn't be more messy? I mean, wouldn't you have to implement something
absurd like a bit of code in yum to read the config value and fiddle
with the presence of the cron script? Ew.

OK, now I think about it, of course the script just checks the config value and exits if it's 'disabled'. Still more Stuff than just a package with the script in it, to my mind, but eh.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to