r496: * Man page cleanups, Closes: #119335

[debhelper.git] / dh_makeshlibs

diff --git a/dh_makeshlibs b/dh_makeshlibs
index a70d3b220be966a0cacfe0ca4d60fd34894467d7..8f0045a8a0fc18f6adb71cdef3613612ee6b3a17 100755 (executable)
--- a/dh_makeshlibs
+++ b/dh_makeshlibs
@@ -11,7 +11,7 @@ use Debian::Debhelper::Dh_Lib;
 
 =head1 SYNOPSIS
 
-  dh_makeshlibs [debhelper options] [-mmajor] [-V[dependancies]] [-n] [-Xitem]
+B<dh_makeshlibs> [S<I<debhelper options>>] [B<-m>I<major>] [B<-V>I<[dependancies]>] [B<-n>] [B<-X>I<item>]
 
 =head1 DESCRIPTION
 
@@ -42,9 +42,15 @@ depend on any particular version of the package containing the shared
 library. It may be necessary for you to add some version dependancy
 information to the shlibs file. If -V is specified with no dependancy
 information, the current version of the package is plugged into a
-dependancy that looks like "packagename (>= packageversion)". If -V is specified with
-parameters, the parameters can be used to specify the exact dependancy
-information needed (be sure to include the package name).
+dependancy that looks like "packagename (>= packageversion)". If -V is
+specified with parameters, the parameters can be used to specify the exact
+dependancy information needed (be sure to include the package name).
+
+Beware of using -V without any parameters; this is a conservative setting
+that always ensures that other packages' shared library dependencies are at
+least as tight as they need to be, so that if the maintainer screws up then
+they won't break. The flip side is that packages might end up with
+dependencies that are too tight and so find it harder to be upgraded.
 
 =item B<-n>, B<--noscripts>