Michael Biebl wrote: > with compat level 7, dh_install will fall back to look for files in > debian/tmp. It's the only dh_install* command that behaves that way > though. Imo all[1] dh_install* commands should behave consistently and fall > back to look for files in debian/tmp, i.e. behave like dh_install
You're looking for a level of consistency that does not make sense amoung debhelper commands. dh_install is also the only command that allows specification of a --srcdir to make it install from a subdirectory. (It has supported this since long before v7.) dh_install is also the only command that allows specifying where to install the files *to*. All the others can figure this out, but it can't So, dh_install is the only command that does something different when debian/install contains debian/tmp/$foo vs src/$foo. Ie, if you list debian/tmp/usr/share/man/man1/foo.1 in debian/manpages, it will be installed to the right place -- which is one reason dh_installman does not need to implicitly look in debian/tmp. dh_installdebconf does not allow specifying any file at all (because it knows where the debconf files are) dh_installdirs only takes a specification of what directories to create. dh_installmodules does not allow specification of files, *or* where they go (it also doesn't actually install anything, at least not currently..) If you have an actual use case, I might consider it. Although dh_install's behavior has made it rather more complicated, and I would have to weigh adding such complexity to a lot of other commands. But a general desire for consistency is not a good reason. -- see shy jo
signature.asc
Description: Digital signature
