Re: how to define inputs for python packages
Am 28.09.20 um 08:05 schrieb Reza Alizadeh Majd: > is there any rule that I missed to choose a dependency as an `input` or > as a `propageted-input` one? This is described in the manual: https://guix.gnu.org/manual/en/html_node/Python-Modules.html#Specifying-Dependencies -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
Re: how to define inputs for python packages
On Mon, Sep 28, 2020 at 09:35:59AM +0330, Reza Alizadeh Majd wrote: > is there any rule that I missed to choose a dependency as an `input` or > as a `propageted-input` one? Hi, I’d say that you always need to declare `python-*` dependencies as `propagated-inputs`, unless it’s something required for building and testing the package, exclusively, in which case the package in question goes to `native-inputs`. As an aside, it’s the same for `r-*` packages. WŻ signature.asc Description: PGP signature
