unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH 2/3] gnu: Add python-pyxb.
Date: Mon, 26 Sep 2016 19:32:03 +0100	[thread overview]
Message-ID: <8760pio6l8.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <bcc8bfa6-c638-e7ff-a48e-6c7d4f2c1038@uq.edu.au>

Ben Woodcroft <b.woodcroft@uq.edu.au> writes:

> On 24/09/16 13:15, Marius Bakke wrote:
>> Ben Woodcroft <b.woodcroft@uq.edu.au> 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.

I'm not sure, we would have to do this with every package that uses
the pysam cython interface. This particular issue is described in the
manual:

https://www.gnu.org/software/guix/manual/html_node/package-Reference.html

The propagated-inputs section says "For example this is necessary when a
C/C++ library needs headers of another library to compile, or when a
pkg-config file refers to another one via its Requires field.".

So I think it's a pretty common propagation scenario. See e.g. 618089f9
for a less convoluted case (C++ library that propagates zlib headers).

Perhaps a "propagated-build-inputs" functionality would be useful, so
that libraries are only propagated at build time and not to the profile.

If we don't do propagation, at least add a comment to python-plastid
explaining that htslib is there to avoid propagating from pysam, since
the plastid code contains no direct references to htslib.

Your other changes LGTM.

Thanks!
Marius

  reply	other threads:[~2016-09-26 18:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 10:10 [PATCH 0/3] gnu: python2-pbcore: Update to 1.2.10 Marius Bakke
2016-09-17 10:10 ` [PATCH 1/3] gnu: python-pysam: Update to 0.9.1.4 Marius Bakke
2016-09-17 10:10 ` [PATCH 2/3] gnu: Add python-pyxb Marius Bakke
     [not found]   ` <3bd16b58-b3d1-d47c-2433-c3a721681463@uq.edu.au>
2016-09-20  6:34     ` Ben Woodcroft
2016-09-20  7:06       ` Ben Woodcroft
2016-09-21 21:14         ` Marius Bakke
2016-09-22  0:46           ` Ben Woodcroft
2016-09-22 15:15             ` Marius Bakke
2016-09-23  1:28               ` Ben Woodcroft
2016-09-23 15:56                 ` Marius Bakke
2016-09-23 16:06                   ` Marius Bakke
2016-09-24  0:23                   ` Ben Woodcroft
2016-09-24  3:15                     ` Marius Bakke
2016-09-26 11:15                       ` Ben Woodcroft
2016-09-26 18:32                         ` Marius Bakke [this message]
2016-09-27 11:01                           ` Ben Woodcroft
2016-09-30 20:12                           ` Ludovic Courtès
2016-09-17 10:10 ` [PATCH 3/3] gnu: python2-pbcore: Update to 1.2.10 Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760pio6l8.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).