debhelper is a collection of programs that can be used in a debian/rules file to automate common tasks related to building binary debian packages. Programs are included to install various files into your package, compress files, fix file permissions, integrate your package with the debian menu system, etc. This will be of use only to debian developers or others who wish to build debian packages.

Debhelper's git repository is now located at: git://

I posted a good overview of debhelper's history in my blog. Here is the thread that started it all.

Colin graphs debhelper statistics here.


version 9.20140817

debhelper 9.20140817 released with these changes

  • Added Portuguese translation of the man pages, by Américo Monteiro. Closes: #758043
  • Updated German translation from Chris Leick. Closes: #735610
version 9.20140809

debhelper 9.20140809 released with these changes

  • dh_perl: Add perlapi-* dependency on packages installed to $Config{vendorarch} Closes: #751684
  • dh_perl: Use vendorlib and vendorarch from Config instead of hardcoding their values. Closes: #750021
  • Typo: Closes: #755237
version 9.20140613

debhelper 9.20140613 released with these changes

  • Pass --disable-silent-rules in dh_auto_configure if DH_VERBOSE is set. Closes: #751207. Thanks, Helmut Grohne.
  • Minor typos. Closes: #741144, #744176
  • dh_installinit: Fix uninitialized value warning when --name is used.

Adding stuff

The tricky thing about maintaining debhelper is that everyone would like to see a program added to it to handle some special-purpose thing, and this is rarely a good idea, since it just serves to increase debhelper's command count, and thus its learning curve, while making me responsible for maintaining support for said obscure thing.

My first rule of thumb is that at least ten packages need to be obvious benefactors of a feature or command before it's added to debhelper. That's an easy bar; after that I have to do some thinking and made the hard call.

TODO: discuss wishlisted commands here