From Fedora Project Wiki
(Just refer to SCG.) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
= Software Collections = | = Software Collections = | ||
{{admon/important|Not approved for Fedora Packages|Please note that official Fedora packages '''must not''' be configured as Software Collection packages. Fedora does not permit relocatable packages, packages using hierarchies that conflict or violate the FHS, or packages storing files in /opt. This | {{admon/important|Not approved for Fedora Packages|Please note that official Fedora packages '''must not''' be configured as Software Collection packages. Fedora does not permit relocatable packages, packages using hierarchies that conflict or violate the FHS, or packages storing files in /opt. This document is '''NOT''' part of the Fedora Packaging Guidelines, and is only here should you wish to generate unofficial Software Collections against Fedora in a third-party repository.}} | ||
== What are Software Collections? == | == What are Software Collections? == | ||
| Line 7: | Line 7: | ||
The concept of Software Collections allows multiple versions of software to be installed at the same time without interfering in any negative way with the standard versions provided by the system. In other words, a Software Collection consists of several components that are "bundled" together and which are expected to work smoothly together without conflicting or overwriting any system files. Installation and updating of Software Collections is managed by RPM. | The concept of Software Collections allows multiple versions of software to be installed at the same time without interfering in any negative way with the standard versions provided by the system. In other words, a Software Collection consists of several components that are "bundled" together and which are expected to work smoothly together without conflicting or overwriting any system files. Installation and updating of Software Collections is managed by RPM. | ||
For detailed information on Software Collections, refer to the [http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Software_Collections_Guide/index.html | For detailed information on Software Collections, refer to the [http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Software_Collections_Guide/index.html Fedora Software Collections Guide]. | ||
[[Category:Packaging]] | [[Category:Packaging]] | ||
Revision as of 14:38, 21 June 2012
Software Collections
Not approved for Fedora Packages
Please note that official Fedora packages must not be configured as Software Collection packages. Fedora does not permit relocatable packages, packages using hierarchies that conflict or violate the FHS, or packages storing files in /opt. This document is NOT part of the Fedora Packaging Guidelines, and is only here should you wish to generate unofficial Software Collections against Fedora in a third-party repository.
Please note that official Fedora packages must not be configured as Software Collection packages. Fedora does not permit relocatable packages, packages using hierarchies that conflict or violate the FHS, or packages storing files in /opt. This document is NOT part of the Fedora Packaging Guidelines, and is only here should you wish to generate unofficial Software Collections against Fedora in a third-party repository.
What are Software Collections?
The concept of Software Collections allows multiple versions of software to be installed at the same time without interfering in any negative way with the standard versions provided by the system. In other words, a Software Collection consists of several components that are "bundled" together and which are expected to work smoothly together without conflicting or overwriting any system files. Installation and updating of Software Collections is managed by RPM.
For detailed information on Software Collections, refer to the Fedora Software Collections Guide.