Package: dh-exec
Version: 0.6
Severity: normal

I tried to use dh_exec with fping 3.4-2 (from experimental):

Currently the debian/rules file has the following command in its install
target:

        install build/ipv4/src/fping debian/fping/usr/bin
        install build/ipv6/src/fping debian/fping/usr/bin/fping6

I tried to replace them with dh_install and the following (executable)
debian/fping.install file:

  #!/usr/bin/dh-exec
  build/ipv4/src/fping usr/bin
  build/ipv6/src/fping => usr/bin/fping6

After that, dh_strip no more strips /usr/bin/fping6 and lintian
correctly complains about that. The permissions were right in the end
due to dh_fixperms though. (So the workaround is likely to call dh_strip
after dh_fixperms.)

After a short discussion on IRC, Gergely found out that dh_exec doesn't
preserve the x-bit due to the usage of File::Copy::copy() instead of
File::Copy::cp(). From the File::Copy POD:

           You may use the syntax "use File::Copy "cp"" to get at the
           "cp" alias for this function. The syntax is exactly the same.
           The behavior is nearly the same as well: as of version 2.15,
           <cp> will preserve the source file's permission bits like the
           shell utility cp(1) would do, while "copy" uses the default
           permissions for the target file (which may depend on the
           process' "umask", file ownership, inherited ACLs, etc.).

Wheezy's perl-modules package contains File::Copy 2.21, but Squeeze
contains 2.14, so this may need a versioned dependency on perl-modules.

(pmvers from the pmtools package helps to find out easily File::Copy's
version.)

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to