|
From: | Hartmut Goebel |
Subject: | Python: inputs vs. propagated inputs |
Date: | Sun, 18 Sep 2016 20:53:56 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hi, I still do not get whether python packages required at run-time
need to be inputs or propagated inputs. In gnu/packages/python.scm there are modules using only inputs (e.g. python-ccm), some are using propagated-inputs (e.g. python-scikit-image), some using both (e.g. python-paramiko). I can not see any clear rule being followed. Also I see a lot of packages defining python-node, python-mock or python-pytest as inputs (e.g. python-mathplotlib). But these package are for tests only and tests AFAIK are never run when cross-compiling. Thus these packages ASAIK are never needed as inputs, only as native-inputs. I'd like to understand when to put a package where and have a clear rule like this: For Python modulesPlease comment on these rules. If we agree on a ruleset, I'll prepare a path for the documentation. -- Regards Hartmut Goebel | Hartmut Goebel | address@hidden | | www.crazy-compilers.com | compilers which you thought are impossible | |
[Prev in Thread] | Current Thread | [Next in Thread] |