From 4f8a46b36e961d1a64d466a63f3a7ef6c90bafe2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 23 Apr 2008 22:49:22 -0400 Subject: dh_prep: New program, does the same as dh_clean -k (which will be deprecated later). --- dh_clean | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'dh_clean') diff --git a/dh_clean b/dh_clean index a08b0b36..78e43c36 100755 --- a/dh_clean +++ b/dh_clean @@ -33,13 +33,8 @@ The debian/clean file can list other files to be removed. =item B<-k>, B<--keep> -Do not delete debian/files, or files listed in debian/clean. When do you -want to use this? Anytime you have a debian/rules that has 2 binary targets -that build different .deb packages; for example, one target is binary-arch, -and the other is binary-indep, or one target builds the shared library, and -the other the -dev package. If you didn't use -k in these cases, then -debian/files would be deleted in the middle, and your changes file will -only contain the last binary package that was built. +This causes L to be run instead of dh_clean, for backwards +compatibility. =item B<-d>, B<--dirs-only> @@ -61,6 +56,12 @@ Delete these files too. =cut init(); +inhibit_log(); + +if ($dh{K_FLAG}) { + # dh_prep will be emulated (mostly) by the code below. + # TODO deprecation warning +} foreach my $package (@{$dh{DOPACKAGES}}) { my $tmp=tmpdir($package); -- cgit v1.2.3