Am 06.04.2018 um 14:12 schrieb Ricardo Wurmus:
> The point here is that in the library case inputs must be propagated,
> whereas in the case where only the executables are used the inputs don’t
> have to be propagated.
>
> Separating them in two outputs doesn’t address this problem as far as I
> ca
Chris Marusich writes:
> Ricardo Wurmus writes:
>
>> we have a bunch of packages that are used both as applications and as
>> Python libraries. An example is “deeptools”.
>
> I took a brief peek at deeptools. It looks like there are programs in
> bin, and libraries in lib. Why can't we just
Am 06.04.2018 um 11:12 schrieb Chris Marusich:
> Why can't we just split them into two
> outputs? For example, put the libraries into the default "out" output
> and the programs into the "bin" output.
For consistence, we should then do this for all other python packages
including a script, e.g. s
Ricardo Wurmus writes:
> we have a bunch of packages that are used both as applications and as
> Python libraries. An example is “deeptools”.
I took a brief peek at deeptools. It looks like there are programs in
bin, and libraries in lib. Why can't we just split them into two
outputs? For ex
Am 04.04.2018 um 22:13 schrieb Ricardo Wurmus:
>> If this is a "pure" application, I'd install it with*out* propagated
>> inputs. This might not be easy to determine, though.
> It is both. It is often used just as an application, but the procedures
> that make up the application are just as often
Hartmut Goebel writes:
> Am 04.04.2018 um 11:36 schrieb Ricardo Wurmus:
>> I wonder how to deal with this. Should we assume that these packages
>> are used as libraries and default to propagating all Python inputs? Or
>> should we have package variants (or outputs?) that propagate inputs as a
Am 04.04.2018 um 11:36 schrieb Ricardo Wurmus:
> I wonder how to deal with this. Should we assume that these packages
> are used as libraries and default to propagating all Python inputs? Or
> should we have package variants (or outputs?) that propagate inputs as a
> side-effect?
If this is a "p
Hi Guix,
we have a bunch of packages that are used both as applications and as
Python libraries. An example is “deeptools”.
As a library we need to propagate other Python inputs; as an application
this is not necessary because we have wrappers.
I wonder how to deal with this. Should we assume
