more exact about rene'ing packages

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3960 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/debian/changelog b/debian/changelog
index bad7a81c58bfc2b882bb781d315a4a96d3776ac9..e8ddf321218e7640da219ee6a0c2d973e84d9bd7 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -35,6 +35,8 @@ developers-reference (3.3.8) unstable; urgency=low
   * Don't use too generic mail ids. Closes: #355725
   * pts/summary is actually used. Thanks, Holger Levsen. Closes: #387108
   * clarify that one should append the NMU-diff to a bug. Closes: #394033
+  * more detailed instructions on binary package removals.
+    Closes: #356643
 
  -- Andreas Barth <aba@not.so.argh.org>  Sat, 11 Nov 2006 10:55:44 -0700
 

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 9db7ba81a48de291d7cf4e8cc3f3249d449b199d..f0a0aa5fc00ec0da4f2aa9e43d5b25ca056d3a34 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.313 $">
+  <!ENTITY cvs-rev "$Revision: 1.314 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2557,13 +2557,18 @@ are not removed from <em>testing</em> directly. Rather, they will be
 removed automatically after the package has been removed from
 <em>unstable</em> and no package in <em>testing</em> depends on it.
        <p>
-If you are simply restructuring a source package so that it no longer
-produces one or more binary packages, there is no need to explicitly ask
-for the packages that are no longer created to be removed.  Such packages
-will be removed when the new package structure has been uploaded into 
-<em>unstable</em> and when no package in <em>testing</em> depends on it.
+There is one exception when an explicit removal request is not necessary:
+If a (source or binary) package is an orphan, it will be removed
+semi-automatically.
+For a binary-package, this means if there is no longer any source package
+producing this binary package;
+if the binary package is just no longer produced on some architectures,
+a removal request is still necessary.
+For a source-package, this means that all binary packages it refers to
+have been taken over by another source package.
         <p>
-You also have to detail the reasons justifying the request. This is to
+In your removal request, you have to detail the reasons justifying the request.
+This is to
 avoid unwanted removals and to keep a trace of why a package has been
 removed. For example, you can provide the name of the package that
 supersedes the one to be removed.