r264 - /web/deps/dep9.mdwn

[sez at users.alioth.debian.org]

Author: sez
Date: Mon Feb  6 20:37:16 2012
New Revision: 264

URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=264
Log:
misc dep9 updates

- elaborate more on transition from update-inetd to reconf-inetd
- rename Open issues section to Clarification of behaviour on package removal
  versus package purge
- add curren status section, with reference to first upload of reconf-inetd


Modified:
    web/deps/dep9.mdwn

Modified: web/deps/dep9.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep9.mdwn?rev=264&op=diff
==============================================================================
--- web/deps/dep9.mdwn (original)
+++ web/deps/dep9.mdwn Mon Feb  6 20:37:16 2012
@@ -186,7 +186,26 @@
 * remove any references of update-inetd in post{inst,rm} scripts;
 * install a reconf-inetd fragment in /usr/share/reconf-inetd, as a regular
   file (ie. not as a conffile);
-* replace the dependency on update-inetd with one on reconf-inetd
+* replace the dependency on update-inetd with one on reconf-inetd (but see
+  notes below)
+
+reconf-inetd will not touch any entries that have not been added by itself,
+including entries added by update-inetd. Thus, a server package that is meant
+to transition from update-inetd to reconf-inetd, must remove any entries that
+it previously added using update-inetd.
+
+Below is an example postinst snippet for an ftp server package that is meant
+to be transitioned from update-inetd to reconf-inetd in release 2.0:
+
+    case $1 in
+        configure)
+            if dpkg --compare-versions "$2" le 2.0; then
+                if which update-inetd; then
+                    update-inetd --remove ftp
+                fi
+            fi
+        ;;
+    esac
 
 
 # xinetd support
@@ -200,18 +219,19 @@
 configuration file implies that any synchronisation requires a user-initiated
 action, and is thus best implemented as a separate tool.
 
-
-# Open issues
+# Clarification of behaviour on package removal versus package purge
 
 According to rules 0 and 1 in the previously listed table, reconf-inetd does
 not distinguish between package removal and purge. In other words,
 /etc/inetd.conf entries that were added by reconf-inetd will be removed upon
-package removal, as long as they have not been locally modified.
-
-Making this distinction so that unmodified inetd.conf entries are removed only
-upon package purge is possible but would incur some extra runtime overhead (to
-find the package in which a reconf-inetd fragment belongs to, and the
-package's state (uninstalled or purged)).
+package removal, as long as they have not been locally modified. Similarly, a
+locally-modified inetd.conf entry will not be removed even if the associated
+package is purged. This is in line with Debian policy, on the basis that
+inetd.conf is a configuration file, but not a conffile.
+
+# Current status
+
+20120206: upload of reconf-inetd to experimental
 
 # Source code repo