No edit summary |
(bundled libraries are private libraries) |
||
| Line 10: | Line 10: | ||
All packages whose upstreams have no mechanism to build against system libraries may opt to carry bundled libraries, but if they do, they must include Provides: bundled(<libname>) = <version> in their RPM spec file. The FPC will maintain the list of bundled provides, please consult with them when adding new provides or in case of disputes. | All packages whose upstreams have no mechanism to build against system libraries may opt to carry bundled libraries, but if they do, they must include Provides: bundled(<libname>) = <version> in their RPM spec file. The FPC will maintain the list of bundled provides, please consult with them when adding new provides or in case of disputes. | ||
Packages that bundle libraries must follow the [[Packaging:AutoProvidesAndRequiresFiltering#Private_Libraries|AutoProvides filtering guidelines]] for private libraries. | |||
= References = | = References = | ||
Revision as of 19:15, 11 November 2015
Bundled Software policy
This policy concerns the use of bundled software in the Fedora Package Collection.
Policy
All packages whose upstreams allow them to be built against system libraries must be built against system libraries.
All packages whose upstreams have no mechanism to build against system libraries must be contacted publicly about a path to supporting system libraries. If upstream refuses, this must be recorded in the spec file using a persistent mechanism to be clarified in the packaging guidelines.
All packages whose upstreams have no mechanism to build against system libraries may opt to carry bundled libraries, but if they do, they must include Provides: bundled(<libname>) = <version> in their RPM spec file. The FPC will maintain the list of bundled provides, please consult with them when adding new provides or in case of disputes.
Packages that bundle libraries must follow the AutoProvides filtering guidelines for private libraries.