pretty sure the wrong package name was put here

[debhelper.git] / debhelper.pod

diff --git a/debhelper.pod b/debhelper.pod
index 45d9241f5cb8ecc52a102d42f3fc3d020ccc4aec..98da7362868ed1d21ce85bc26bd4721203d9f0c3 100644 (file)
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -191,14 +191,12 @@ in ALL packages acted on, not just the first.
 
 =head1 BUILD SYSTEM OPTIONS
 
 
 =head1 BUILD SYSTEM OPTIONS
 

-All of the B<dh_auto_>I<*> debhelper programs set environment variables
-listed by B<dpkg-buildflags>, unless they are already set. They
-support DEB_BUILD_OPTIONS=noopt too.
-

 The following command line options are supported by all of the B<dh_auto_>I<*>
 debhelper programs. These programs support a variety of build systems,
 and normally heuristically determine which to use, and how to use them.
 You can use these command line options to override the default behavior.
 The following command line options are supported by all of the B<dh_auto_>I<*>
 debhelper programs. These programs support a variety of build systems,
 and normally heuristically determine which to use, and how to use them.
 You can use these command line options to override the default behavior.

+Typically these are passed to L<dh(1)>, which then passes them to all the 
+B<dh_auto_>I<*> programs.

 
 =over 4
 
 
 =over 4
 


@@ -476,8 +474,15 @@ multiarch directories to autoconf in --libdir and --libexecdir.
 
 =item -
 
 
 =item -
 

-dh supports use of standard targets in debian/rules without needing
-to manually define the dependencies between targets there.
+dh is aware of the usual dependencies between targets in debian/rules.
+So, "dh binary" will run any build, build-arch, build-indep, install,
+etc targets that exist in the rules file. There's no need to define an
+explicit binary target with explicit dependencies on the other targets.
+
+=item -
+
+B<dh_strip> compresses debugging symbol files to reduce the installed
+size of -dbg packages.

 
 =item -
 
 
 =item -
 


@@ -488,6 +493,17 @@ in --libexecdir when using autoconf.
 
 B<dh> does not default to enabling --with=python-support
 
 
 B<dh> does not default to enabling --with=python-support
 

+=item -
+
+All of the B<dh_auto_>I<*> debhelper programs and B<dh> set
+environment variables listed by B<dpkg-buildflags>, unless
+they are already set. They support DEB_BUILD_OPTIONS=noopt too.
+
+=item -
+
+B<dh_auto_configure> passes CFLAGS to perl F<Makefile.PL> and
+F<Build.PL>
+

 =back
 
 =back
 =back
 
 =back


@@ -609,13 +625,10 @@ Set to B<1> to enable no-act mode.
 =item B<DH_OPTIONS>
 
 Anything in this variable will be prepended to the command line arguments
 =item B<DH_OPTIONS>
 
 Anything in this variable will be prepended to the command line arguments

-of all debhelper commands. Command-specific options will be ignored by 
-commands that do not support them. 
+of all debhelper commands.

 
 

-This is useful in some situations, for example, if you need to pass B<-p> to
-all debhelper commands that will be run. One good way to set B<DH_OPTIONS> is
-by using "Target-specific Variable Values" in your F<debian/rules> file. See
-the make documentation for details on doing this.
+When using L<dh(1)>, it can be passed options that will be passed on to each
+debhelper command, which is generally better than using DH_OPTIONS.

 
 =item B<DH_ALWAYS_EXCLUDE>
 
 
 =item B<DH_ALWAYS_EXCLUDE>