A small contribution. But what can dh_installdebconf do to detect other 
features used? It would need to parse and analyse the scripts to be sure. Is 
grepping for certain strings, such as debconf-escape, enough?

-- 
Magnus Holmgren        [EMAIL PROTECTED]
--- dh_installdebconf	2006-03-15 22:11:47.000000000 +0100
+++ dh_installdebconf	2007-03-21 15:09:03.968393305 +0100
@@ -69,6 +69,8 @@
 	@[EMAIL PROTECTED];
 }
 
+my $min_debconfver = "0.005";
+
 foreach my $package (@{$dh{DOPACKAGES}}) {
 	my $tmp=tmpdir($package);
 	my $config=pkgfile($package,"config");
@@ -92,6 +94,7 @@
 		
 		if (-d "debian/po") {
 			complex_doit("po2debconf @extraparams $templates > $tmp/DEBIAN/templates");
+			$min_debconfver = "1.002.0" if $min_debconfver lt "1.002.0";
 		}
 		else {
 			doit("install", "-o", 0, "-g", 0, "-m", 644, "-p",
@@ -99,9 +102,8 @@
 		}
 	}
 
-	# I'm going with debconf 0.5 because it was the first
-	# "modern" one. udebs just need cdebconf.
-	my $debconfdep=is_udeb($package) ? "cdebconf-udeb" : "debconf (>= 0.5) | debconf-2.0";
+	$min_debconfver =~ s/(^|\.)0+(?!$)/$1/g;
+	my $debconfdep=is_udeb($package) ? "cdebconf-udeb" : "debconf (>= $min_debconfver) | debconf-2.0";
 	if ($config ne '' || $templates ne '') {
 		addsubstvar($package, "misc:Depends", $debconfdep);
 	}

Attachment: pgpb1f3mnhW4C.pgp
Description: PGP signature

Reply via email to