How to remove a package at end of life

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m (Fixed numbered list formatting)
Line 5: Line 5:
 
For this example, we'll remove the package ''foo''.
 
For this example, we'll remove the package ''foo''.
  
1. Make sure it is properly Obsoleted/Provided by something if it is being replaced, see [http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-3cfc1ea19d28975faad9d56f70a6ae55661d3c3d Renaming/Replacing Guidelines] .
+
# Make sure the package is properly Obsoleted/Provided by something if it is being replaced, see [http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-3cfc1ea19d28975faad9d56f70a6ae55661d3c3d Renaming/Replacing Guidelines].
1. Add a <code>dead.package</code> file to CVS in affected <code>foo/*</code> branches (usually <code>foo/devel</code> only).  This should briefly explain where this package went:  'Obsolete package.', 'Renamed to bar' or the like.
+
# Add a <code>dead.package</code> file to CVS in affected <code>foo/*</code> branches (usually <code>foo/devel</code> only).  The contents of this file should briefly explain where this package went:  'Obsolete package.', 'Renamed to bar' or the like.
1. <code>cvs rm</code> all the other files in the <code>foo/*</code> branches that you added <code>dead.package</code> to.  This should help make it clearly obvious what's going on here.  It's not necessary to remove the files in other branches, unless there are other factors at work.  (e.g., licensing issue, package being removed completely from Fedora.)
+
# <code>cvs rm</code> all the other files in the <code>foo/*</code> branches that you added <code>dead.package</code> to.  This should help make it clearly obvious what's going on here.  It's not necessary to remove the files in other branches, unless there are other factors at work.  (e.g., licensing issue, package being removed completely from Fedora.)
1. Remove the package from [[PackageMaintainers/CompsXml| comps]]  if it is listed.
+
# Remove the package from [[PackageMaintainers/CompsXml| comps]]  if it is listed.
1. Mark the package as "retired" on ["PackageMaintainers/RetiredPackages"] . Do not mark the package this way if it is just being renamed in some but not all distro branches.
+
# Mark the package as "retired" on [[PackageMaintainers/RetiredPackages | Retired Packages]] . Do not mark the package this way if it is just being renamed in some but not all distro branches.
1. Send mail to rel-eng@fedoraproject.org asking the package to be blocked from the appropriate collections in which it is retired.
+
# Send mail to rel-eng@fedoraproject.org asking the package to be blocked from the appropriate collections in which it is retired.

Revision as of 03:30, 29 May 2008

When a package reaches the end of its useful life, the following steps will let other people -- and automated processes! -- know both not to expect any more releases, and why it was removed. The process is simple.

For this example, we'll remove the package foo.

  1. Make sure the package is properly Obsoleted/Provided by something if it is being replaced, see Renaming/Replacing Guidelines.
  2. Add a dead.package file to CVS in affected foo/* branches (usually foo/devel only). The contents of this file should briefly explain where this package went: 'Obsolete package.', 'Renamed to bar' or the like.
  3. cvs rm all the other files in the foo/* branches that you added dead.package to. This should help make it clearly obvious what's going on here. It's not necessary to remove the files in other branches, unless there are other factors at work. (e.g., licensing issue, package being removed completely from Fedora.)
  4. Remove the package from comps if it is listed.
  5. Mark the package as "retired" on Retired Packages . Do not mark the package this way if it is just being renamed in some but not all distro branches.
  6. Send mail to rel-eng@fedoraproject.org asking the package to be blocked from the appropriate collections in which it is retired.