Am 02.10.2016 um 04:27 schrieb Leo Famulari: > I will test a few packages and, if they work, I plan to create a > python-build-system job on Hydra and try building it the entire > package tree (assuming that Hydra has the capacity).
Please note that you need to add Marius' patches [1] to make this work at all. Mine had some errors :-( [1] http://lists.gnu.org/archive/html/guix-devel/2016-09/msg02290.html >> A) For python2 include python2-setuptools as a native-input by default. > Do all python-2 packages require setuptools, or just most of them? As I wrote in my follow-up correction, I implemented a different strategy: pip and setuptools are now installed as part of python2, like it is the default in Python 3. > >> C) Strip python-setuptools and python2-setuptools from all native-inputs >> defined in packages. > Hydra will test this :) Great, since this is a computer's job :-) >> * update Python to 2.7.12 and 3.4.5. > Python 2.7.12 and 3.5.2 are on core-updates. Should I cherry-pick those > changes will testing these patches? Or should they work with the Python > packages that we have on master? It should work both ways. I'll rebase and cleanup my by patch set later, anyway, so we can verify then. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
