[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: python-pytest in references graph
From: |
Roel Janssen |
Subject: |
Re: python-pytest in references graph |
Date: |
Mon, 25 Jul 2022 07:59:49 +0200 |
User-agent: |
Evolution 3.44.3 (3.44.3-1.fc36) |
On Sun, 2022-07-24 at 23:01 +0200, Maxime Devos wrote:
>
> On 24-07-2022 22:25, Roel Janssen wrote:
> > I'm trying to understand the output of:
> > $ guix graph --type=references python-rdflib | dot -Tsvg -o rdflib.svg
> >
> > Particularly, I'm looking at why python-pytest has an input arrow from
> > python-rdflib, while it's
> > "only" a native-input? I thought the "references" graph type would only
> > include run-time
> > references, but I don't know what happens in this case.
> >
> > What am I missing?
>
> It should, but sometimes there are bugs in the package definition or
> build system, in this case causing python-rdflib to refer to the
> native-input python-pytest. Likely it's the 'add-install-to-path' phase
> adding too much, a known issue, which could be solved by separating
> inputs and native-inputs on the build side when compiling natively (and
> not only when cross-compiling) (currently they are merged together into
> 'inputs'), though non-trivial.
Thanks for your explanation! I see indeed that in the build output a couple
of programs include pytest in their "GUIX_PYTHONPATH".
Kind regards,
Roel Janssen