Toll Free Numbers
  • Last 5 Forum Topics
    Last post

The Web Only This Site



  • MARC

    Mailing list ARChives
    - Search by -


    Computing Dictionary

  • Text Link Ads
  • LINUX man pages
  • Linux Man Page Viewer

    The following form allows you to view linux man pages.





           dh sequence [--with addon[,addon ...]] [--list] [debhelperoptions]


           dh runs a sequence of debhelper commands. The supported sequences
           correspond to the targets of a debian/rules file: build-arch, build-
           indep, build, clean, install-indep, install-arch, install, binary-arch,
           binary-indep, and binary.


           A debian/rules file using dh can override the command that is run at
           any step in a sequence, by defining an override target.
           To override dh_command, add a target named override_dh_command to the
           rules file. When it would normally run dh_command, dh will instead call
           that target. The override target can then run the command with
           additional options, or run entirely different commands instead. See
           examples below.  (Note that to use this feature, you should Build-
           Depend on debhelper 7.0.50 or above.)
           Override targets can also be defined to run only when building
           architecture dependent or architecture independent packages.  Use
           targets with names like override_dh_command-arch and
           override_dh_command-indep.  (Note that to use this feature, you should
           Build-Depend on debhelper 8.9.7 or above.)


           --with addon[,addon ...]
               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, or multiple addons can be
               listed, separated by commas.  This is used when there is a third-
               party package that provides debhelper commands. See the PROGRAMMING
               file for documentation about the sequence addon interface.
           --without addon
               The inverse of --with, disables using the given addon. This option
               can be repeated more than once, or multiple addons to disable can
               be listed, separated by commas.
           --list, -l
               List all available addons.
               Prints commands that would run for a given sequence, but does not
               run them.
           Other options passed to dh are passed on to each command it runs. This
           can be used to set an option like -v or -X or -N, as well as for more
           specialised options.


                   #!/usr/bin/make -f
                           dh $@
                           dh_strip -Xfoo
                           dh_auto_configure -- --with-foo --disable-bar
           Sometimes the automated dh_auto_configure(1) and dh_auto_build(1) can't
           guess what to do for a strange package. Here's how to avoid running
           either and instead run your own commands.
                   #!/usr/bin/make -f
                           dh $@
                           make universe-explode-in-delight
           Another common case is wanting to do something manually before or after
           a particular debhelper command is run.
                   #!/usr/bin/make -f
                           dh $@
                           chmod 4755 debian/foo/usr/bin/foo
           If your package uses autotools and you want to freshen config.sub and
           config.guess with newer versions from the autotools-dev package at
           build time, you can use some commands provided in autotools-dev that
           automate it, like this.
                   #!/usr/bin/make -f
                           dh $@ --with autotools_dev
           Python tools are not run by dh by default, due to the continual change
           in that area. (Before compatibility level v9, dh does run
           dh_pysupport.)  Here is how to use dh_python2.
                   #!/usr/bin/make -f
                   #!/usr/bin/make -f
                           dh $@ --sourcedirectory=src
           And here is an example of how to tell the dh_auto_* commands to build
           in a subdirectory, which will be removed on clean.
                   #!/usr/bin/make -f
                           dh $@ --builddirectory=build
           If your package can be built in parallel, you can support parallel
           building as follows. Then dpkg-buildpackage -j will work.
                   #!/usr/bin/make -f
                           dh $@ --parallel
           Here is a way to prevent dh from running several commands that you
           don't want it to run, by defining empty override targets for each
                   #!/usr/bin/make -f
                           dh $@
                   # Commands not to run:
                   override_dh_auto_test override_dh_compress override_dh_fixperms:
           A long build process for a separate documentation package can be
           separated out using architecture independent overrides.  These will be
           skipped when running build-arch and binary-arch sequences.
                   #!/usr/bin/make -f
                           dh $@
                           $(MAKE) -C docs
                   # No tests needed for docs
                           $(MAKE) -C docs install
           Adding to the example above, suppose you need to chmod a file, but only
           when building the architecture dependent package, as it's not present
           when building only documentation.
           --remaining options can override this behavior.
           A sequence can also run dependent targets in debian/rules.  For
           example, the "binary" sequence runs the "install" target.
           dh uses the DH_INTERNAL_OPTIONS environment variable to pass
           information through to debhelper commands that are run inside override
           targets. The contents (and indeed, existence) of this environment
           variable, as the name might suggest, is subject to change at any time.
           Commands in the build-indep, install-indep and binary-indep sequences
           are passed the -i option to ensure they only work on architecture
           independent packages, and commands in the build-arch, install-arch and
           binary-arch sequences are passed the -a option to ensure they only work
           on architecture dependent packages.


           The following options are deprecated. It's much better to use override
           targets instead.
           --until cmd
               Run commands in the sequence until and including cmd, then stop.
           --before cmd
               Run commands in the sequence before cmd, then stop.
           --after cmd
               Run commands in the sequence that come after cmd.
               Run all commands in the sequence that have yet to be run.
           In the above options, cmd can be a full name of a debhelper command, or
           a substring. It'll first 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.


           This program is a part of debhelper.


           Joey Hess <>

    9.20120115ubuntu3 2012-01-15 DH(1)


  • Linux

    The Distributions


    The Software


    The News


  • Toll Free

Toll Free Numbers
Copyright © 1999 - 2016 by LinuxGuruz