On 24/09/16 13:15, Marius Bakke wrote:
Ben Woodcroft <address@hidden> writes:
Htslib is propagated because it
is included by the installed samtools and bcftools headers; at least one
of pysams dependencies failed to build when it was a regular input.
Ah, I see. Can this be avoided with patchelf?
I don't think so. The htslib headers need to be propagated for anything
that uses header files from pysam, since they contain contain code such
as "include <htslib/foo.h>". Perhaps you can update the comment to make
it more clear?
Patchelf is probably what made that work when htslib was bundled.
Ah, ok I see, so the problem is that python-plastid requires the .h
files during build. Given that this is the only package that has an
issue, and perhaps pysam doesn't intend to provide these .h files as
part of it's "interface", I think it might be best to simply put htslib
as an input to python-plastid.