diff --git a/man/dpkg-maintscript-helper.1 b/man/dpkg-maintscript-helper.1
index e3a9b12..6c7d8e1 100644
--- a/man/dpkg-maintscript-helper.1
+++ b/man/dpkg-maintscript-helper.1
@@ -28,6 +28,8 @@ dpkg\-maintscript\-helper \- works around known dpkg limitations in maintainer s
 \fBrm_conffile\fP \fIconffile\fP [\fIprior-version\fP [\fIpackage\fP]]
 .P
 \fBmv_conffile\fP \fIold-conffile\fP \fInew-conffile\fP [\fIprior-version\fP [\fIpackage\fP]]
+\P
+\fBsymlink_to_dir\fP \fIold-symlink\fP \fIold-target\fP [\fIprior-version\fP [\fIpackage\fP]]
 .
 .SH DESCRIPTION
 .P
@@ -145,6 +147,52 @@ to \fInew-conffile\fP if \fIold-conffile\fP is still available. On
 abort\-upgrade/abort\-install, the \fBpostrm\fP renames
 \fIold-conffile\fP\fB.dpkg\-remove\fP back to \fIold-conffile\fP if required.
 .
+.SH SYMLINKS AND DIRECTORY CONVERTION
+.
+When upgrading a package, \fBdpkg\fP will not automatically convert a symlink 
+to a directory or vice-versa.
+.
+.SS Converting a symlink to directory
+.
+If a symlink is converted to a real directory, you need to make sure
+before unpacking the symlink is removed. This may seem a simple
+change to the \fBpreinst\fP script at first, however that will result in
+some problem in case of admin local customisation of the symlink or
+in case of downgrading the package.
+.P
+Graceful renaming can be implemented by putting the following shell
+snippet in the \fBpreinst\fP, \fBpostinst\fP and \fBpostrm\fP maintainer
+scripts:
+.P
+    dpkg\-maintscript\-helper symlink_to_dir \\
+        \fIold-symlink\fP \fIold-target\fP \fIprior-version\fP \fIpackage\fP \-\- "$@"
+.P
+\fIold-symlink\fP and \fIold-target\fP are the name of the
+of the old symlink (will be at end of install a directory) and old-target 
+the target of the former symlink.
+.P
+\fIprior-version\fP defines the latest version of the package whose upgrade
+should trigger the rename of the conffile (see the notes for
+\fBrm_conffile\fR above concerning the correct value). If \fIprior-version\fP
+is empty or omitted, then the operation is tried on every upgrade (note: it's
+safer to give the version and have the operation tried only once).
+.P
+\fIpackage\fP is the package name. When the package is "Multi-Arch: same",
+this parameter must include the architecture qualifier. If empty or
+omitted, the \fBDPKG_MAINTSCRIPT_PACKAGE\fP environment variable (as set
+by \fBdpkg\fP) will be used.
+.P
+All the parameters of the maintainer scripts have to be forwarded to the
+program after \fB\-\-\fP.
+.P
+Current implementation: the \fBpreinst\fP checks if the symlink exists
+and points to \fBold-target\fP, if no it's left on place otherwise it's renamed to
+\fIold-symlink\fP\fB.dpkg\-remove\fP. On configuration, the \fBpostinst\fP
+removes \fIold-symlink\fP\fB.dpkg\-remove\fP if \fIold-symlink\fP\fB.dpkg\-remove\fP 
+is still a symlink. On
+abort\-upgrade/abort\-install, the \fBpostrm\fP renames
+\fIold-symlink\fP\fB.dpkg\-remove\fP back to \fIold-symlink\fP if required.
+.
 .SH INTEGRATION IN PACKAGES
 .P
 Given that \fBdpkg\-maintscript\-helper\fP is used in the \fBpreinst\fP,