|author||Joey Hess <email@example.com>||2009-04-20 16:05:24 -0400|
|committer||Joey Hess <firstname.lastname@example.org>||2009-04-20 16:05:24 -0400|
Move dh sequence documentation to PROGRAMMING.
3 files changed, 24 insertions, 34 deletions
diff --git a/debian/changelog b/debian/changelog
index 5321bdb..afe27c1 100644
@@ -3,6 +3,7 @@ debhelper (7.2.8) UNRELEASED; urgency=low
* dh_desktop: Now a deprecated no-op, since desktop-file-utils
uses triggers. Closes: #523474
(also Closes: #521960, #407701 as no longer applicable)
+ * Move dh sequence documentation to PROGRAMMING.
-- Joey Hess <email@example.com> Tue, 31 Mar 2009 14:07:13 -0400
@@ -50,8 +50,8 @@ you should Build-Depend on debhelper 7.0.50 or above.)
Add the debhelper commands specified by the given addon to appropriate places
in the sequence of commands that is run. This option can be repeated more
than once, and is used when there is a third-party package that provides
-debhelper commands. See "SEQUENCE ADDONS" below for documentation about what
-such packages should do to be supported by --with.
+debhelper commands. See the PROGRAMMING file for documentation about
+the sequence addon interface.
=item B<--until> I<cmd>
@@ -82,26 +82,6 @@ search for a command in the sequence exactly matching the name, to avoid any
ambiguity. If there are multiple substring matches, the last one in the
sequence will be used.
-=head1 SEQUENCE ADDONS
-When B<--with> I<addon> is used, dh loads the perl module
-Debian::Debhelper::Sequence::I<addon>. Two functions are provided to let
-the module add its commands to sequences:
-=item Debian::Debhelper::Dh_Lib::insert_before(existing_command, new_command)
-Insert I<new_command> in sequences before I<existing_command>.
-=item Debian::Debhelper::Dh_Lib::insert_after(existing_command, new_command)
-Insert I<new_command> in sequences after I<existing_command>.
-Remove I<existing_command> from the list of commands to run.
diff --git a/doc/PROGRAMMING b/doc/PROGRAMMING
index 5c60a0b..9963181 100644
@@ -46,27 +46,19 @@ Debhelper programs should default to doing exactly what policy says to do.
There are always exceptions. Just ask me.
-Dh_Lib.pm is the library used by all debhelper programs to parse their
+Dh_Lib is the library used by all debhelper programs to parse their
arguments and set some useful variables. It's not mandatory that your
program use Dh_Lib.pm, but it will make it a lot easier to keep it in sync
with the rest of debhelper if it does, so this is highly encouraged.
-(There used to be a version of Dh_lib.pm that was a library of functions for
-shell scripts. If you want to write a debhelper command that is a shell
-script, I can dig up that old library for you. Only the perl one is
-supported now, though.)
-Use Dh_Lib.pm like this:
+Use Dh_Lib like this:
-The BEGIN block is there to make perl look for the module in all the right
The init() function causes Dh_lib to parse the command line and do some other
@@ -258,4 +250,21 @@ write_log($cmd, $package ...)
Writes the log files for the specified package(s), adding
the cmd to the end.
+The dh(1) command has a --with <addon> parameter that ca be used to load
+a sequence addon named Debian::Debhelper::Sequence::<addon>.
+These addons can add/remove commands to the dh command sequences, by calling
+some functions from Dh_Lib:
+ Insert $new_command in sequences before $existing_command
+ Insert $new_command in sequences after $existing_command
+ Remove $existing_command from the list of commands to run.
-- Joey Hess <firstname.lastname@example.org>