X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=dh_auto_clean;h=ddf78699daaba2ad80c235b29631b39423cbc387;hb=e14e51cc8d91ac28fb215ef27233f3ee3204cf11;hp=8603b1119a8963d2978fd3b42e804045ea3ccf55;hpb=d92a7906608dcf6c697e912f73376c7f6b030fa8;p=debhelper.git diff --git a/dh_auto_clean b/dh_auto_clean index 8603b11..ddf7869 100755 --- a/dh_auto_clean +++ b/dh_auto_clean @@ -7,6 +7,7 @@ dh_auto_clean - automatically cleans up after a build =cut use strict; +use Debian::Debhelper::Dh_Lib; use Debian::Debhelper::Dh_Buildsystems; =head1 SYNOPSIS @@ -15,33 +16,34 @@ B [S>] [S>] [S =head1 DESCRIPTION -dh_auto_clean is a debhelper program that tries to automatically clean up +B is a debhelper program that tries to automatically clean up after a package build. It does so by running the appropriate command for the build system it detects the package uses. For example, if there's a -Makefile and it contains a "distclean", "realclean", or "clean" target, -then this is done by running make (or MAKE, if the environment variable is -set). If there is a setup.py or Build.PL, it is run to clean the package. +F and it contains a B, B, or B target, +then this is done by running B (or B, if the environment variable is +set). If there is a F or F, it is run to clean the package. This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong clean target, you're encouraged to skip using -dh_auto_clean at all, and just run make clean manually. +B at all, and just run B manually. =head1 OPTIONS -See L for a list of common build +See L> for a list of common build system selection and control options. =over 4 =item B<--> I -Pass "params" to the program that is run. These can be used to supplement -or override the any standard parameters that dh_auto_clean passes. +Pass I to the program that is run. These can be used to supplement +or override the any standard parameters that B passes. =back =cut +inhibit_log(); buildsystems_init(); buildsystems_do();