[Guidelines Change] Changes to the Packaging Guidelines

Tom Callaway tcallawa at redhat.com
Thu Dec 9 14:46:20 UTC 2010

Here are the latest set of changes to the Fedora Packaging Guidelines:


A new page has been added which describes how to deal with bundled
libraries when you find them in your package:


Some clarification has been added to the sections dealing with bundled
libraries, specifically that:

In this RPM packaging context, the definition of the term 'library'
includes: compiled third party source code resulting in shared or static
linkable files, interpreted third party source code such as Python, PHP
and others. At this time JavaScript intended to be served to a web
browser is specifically exempted from this but this will likely change
in the future.


Also, a note was added to make it clear that multiple licensing
scenarios may be a good indicator of a bundled library situation:



A section has been added to the Packaging:Guidelines#Changelog entry
describing the acceptable methods of having multiple changelog entries
per release:



A new example of a reason an exception for bundling libraries might be
granted has been added to the guidelines.  If the library is being
bundled because it is a snapshot of a newer release of the library
needed for new features, you may have grounds for an exception.  See the
complete policy for details on when an exception might be granted for
this reasoning.



Fedora has always implied that the update path from Fedora release to
Fedora release and from Fedora release to updates should be maintained
but there wasn't an explicit statement in the Guidelines.  Well, there
is now.



The guidelines have been updated to indicate that %doc files must not
have executable permissions.



The section on Requiring Base Package was clarified, as the original
language involving -libs packages may have been confusing:



These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).

Many thanks to Steven Garcia, Nils Philippsen, FESCo 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:



More information about the devel-announce mailing list