On Thu, 24 Mar 2016 19:59:29 +0100 Christian Hofstaedtler
<[email protected]> wrote:
>
> Dear Maintainer,
Hello Christian,
>
> Your package ruby-selinux has an implicit version-specific
> dependency on librubyX.Y, but doesn't declare it in Depends:.
>
> Please add Depends: librubyA.A | librubyB.B | ... to ruby-selinux
> as appropriate for the versions of ruby you're shipping extensions
> for.
>
> The easiest way of adding those dependencies might be by actually
> linking with librubyX.Y, even if the extension.so doesn't use any of
> libruby's symbols. While I see your package uses swig to build the
> .so, I don't know enough swig to propose a patch.
I'm not really sure that adding unnecessary link to libraries is the way
to go.
Shouldn't this be handled by dh_ruby (like dh_python is doing) by
looking where files on the filesystem are installed and add the
necessary dependencies? Also should this dependency be against
librubyX.X or against the ruby interpreter itself?
I'm thinking about reassigning this to gem2deb pkg.
Cheers,
Laurent Bigonville
_______________________________________________
SELinux-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/selinux-devel
