mean the package must build-depend on a new enough version of binutils.
Closes: #231382
* dh_installdebconf: The debconf dependency has changed to include
"| debconf-2.0". Closes: #230622
}
}
+ # I'm going with debconf 0.5 because it was the first
+ # "modern" one.
+ my $debconfdep="debconf (>= 0.5) | debconf-2.0";
if ($config ne '' || $templates ne '') {
- # I'm going with debconf 0.5 because it was the first
- # "modern" one.
- addsubstvar($package, "misc:Depends", "debconf", ">= 0.5");
+ addsubstvar($package, "misc:Depends", $debconfdep);
}
else {
- addsubstvar($package, "misc:Depends", "debconf", ">= 0.5", 1); # remove
+ addsubstvar($package, "misc:Depends", $debconfdep, undef, 1); # remove
}
if (($config ne '' || $templates ne '') && ! $dh{NOSCRIPTS}) {
a dependency on the correct base package. This is only necessary for some
packages that are included in the base system.
+Note that this flag may cause no dependency on perl-base to be generated at
+all. perl-base is Essential, so its dependency can be left out, unless a
+versioned dependency is needed.
+
=item B<-V>
By default, scripts and architecture independent modules don't depend
This option may be repeated to list more than one package.
+Note that if you use this option, your package should build-depend on
+binutils (>= 2.12.90.0.9).
+
=item B<-k>, B<--keep-debug>
Debug symbols will be retained, but split into an independant
file in usr/lib/debug/ in the package build directory. --dbg-package
is easier to use than this option, but this option is more flexible.
+Note that if you use this option, your package should build-depend on
+binutils (>= 2.12.90.0.9).
+
=back
=head1 NOTES