I have been looking into cron jobs in the distribution and I noticed
that there dont seem to be any packaging guidelines for packaging cron
jobs in the distribution.
More or less every package that ships cron jobs does not require Cronie
which arguably it should, however only few packages actually strictly
need cron ( logwatch,leafnote etc ) while the majority of them are more
or less small administration task that can be triggered manually by the
user/administrator thus not strictly required by the component.
Before I start providing patches to fix this I need to know what is the
correct way to move forward as in...
Should the requirement on Cronie be added to the spec file?
Should those cron-jobs be package in a separate sub package which would
depend on Cronie?
Some more changes to the Fedora Packaging Guidelines have been made:
The Packaging Guidelines covering Desktop files have been amended to say
that for Fedora 19 and beyond, the vendor tag must not be used. If it
was being used in a previous release, it may continue to be used for
that previous release, but must be removed in Fedora 19. New packages
must not add the vendor tag for any release. Packagers are reminded that
they must not change the name of the desktop file in a stable Fedora
The Ruby Guidelines have been updated to prepare for JRuby integration
in Fedora (and new macros to assist in this).
The Java Guidelines have been changed to reflect BuildRequires:
maven-local (instead of maven).
These guideline changes were approved by the Fedora Packaging
Many thanks to Bohuslav Kabrda, Parag Nemade, Stanislav Ochotnicky, and
all of the members of the FPC, for assisting in drafting, refining, and
passing these guidelines.
As a reminder: The Fedora Packaging Guidelines are living documents! If
you find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here: