On Fri, Mar 15, 2013 at 10:55:57AM -0500, Jon Ciesla wrote: > On Fri, Mar 15, 2013 at 10:48 AM, Daniel P. Berrange <berrange@xxxxxxxxxx>wrote: > > > On Fri, Mar 15, 2013 at 10:45:03AM -0500, Jon Ciesla wrote: > > > On Fri, Mar 15, 2013 at 10:30 AM, Miloslav Trmač <mitr@xxxxxxxx> wrote: > > > > > > > On Fri, Mar 15, 2013 at 4:11 PM, Daniel P. Berrange < > > berrange@xxxxxxxxxx> > > > > 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. > > > > > > > > > > More to the point, > > > https://fedoraproject.org/wiki/Starting_services_by_default > > > > That's about starting system services by default though, so isn't > > directly relevant to the question of whether cron jobs are allowed > > to be enabled by default. Do we have any package docs about cron > > job enablement ? I couldn't find any in my search attempts. > > > > I guess I always took that to include cron jobs, but you're right, it > doesn't explicitly say so. Maybe this needs clarification. Yep, I think it would be worth explicitly documenting requirements around cron jobs in the packaging guidelines, if we want to have any rules in this area. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
