Policy proposal for compatibility packages

Thorsten Leemhuis fedora at leemhuis.info
Wed Jan 2 16:52:27 UTC 2008


On 02.01.2008 17:21, Brian Pepple wrote:
> Here's a proposal for the handling of new compat packages:
> http://fedoraproject.org/wiki/BrianPepple/DraftCompatPackages

Below the proposal text cut'n'pasted from the wiki for easier review and
here on the list (as discussed in
https://www.redhat.com/archives/fedora-devel-list/2007-December/msg01269.html

and written down in
http://fedoraproject.org/wiki/Development/Schedule/MeetingGuidelines ).

---

= Compatibility Packages Draft =
[[TableOfContents()]]

= Overview =

== Problem Space ==
## Describe the problem this proposal seeks to solve
Compatibility packages are packages which provide a secondary (usually
older) version of an API or program from the primary version packaged
within Fedora. Currently, there are no formal guidelines in regards to
the creation of them.

== Solution Overview ==
## Describe in brief the solution proposed
In general, software within Fedora should be moved to run on the current
version of libraries. Shipping multiple versions of libraries tends to
be problematic due to a potential case where multiple versions of a
library could be linked into one running process leading to
unpredictable results. It also means that security changes, fixes, etc.
They also take more repository space, requiring more download of package
metadata, ...

In cases where this isn't possible, a compatibility package _may_ be
introduced if there is someone who is willing to maintain the
compatibility package and the primary package maintainer is not against
the idea. The reasoning for the latter is that even if the primary
maintainer is not maintaining the compatibility package, chances are
that they will have to be involved in the maintenance due to passing
along security problems, helping out with things and redirecting
misfiled bugs.  If the compatibility packager and the primary package
maintainer cannot come to a mutual decision, it can be escalated to
FESCo to make the final decision.

== Scope ==
## Describe the scope of what all things will be effected by the proposal
This proposal would only affect the creation of new compatibility packages.

== Comments ? ==
## A section provided for comments

---

CU
knurd




More information about the devel mailing list