Morning! Ricardo Wurmus <rek...@elephly.net> skribis:
> Ludovic Courtès <l...@gnu.org> writes: [...] >> So what are the options? If we get a bug-fix for Guile’s compiler >> today, does it help? If we graft it then we can deliver it without >> having to wait for a Guile release, which helps a bit? >> >> I think it’s all about time: we could wait (and hack!) some more, and >> solve the root problem. This is the best long-term course of action, >> but at the same time it delays the Guix release. > > The way I see it, having very large modules like (gnu packages python) > is not desirable anyway. So we won’t get around distributing package > definitions. If we can get a fix for Guile soon that’s great, but we > should begin moving packages independent of that. Right, that makes sense. >> Actually, we could do similarly for Perl and Python: >> python-web, python-check, python-crypto, etc. > > Okay. I’ll leave that task for someone else, because I don’t think I > can do more than haskell.scm today. I’ve moved 129 packages from python.scm to python-web.scm: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=1b2f753d9c73a5431ec1f5510449c480debf80ce There are still 863 left in python.scm, and it would be good to be at 400–500 max. I’ll see if I can do python-crypto or python-check today. Thank you for your work on haskell.scm and perl.scm! Ludo’.
