From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#27284: Memory leak in 'guix pull' or 'make' in guix source Date: Tue, 14 Nov 2017 08:54:57 +0100 Message-ID: <87bmk5fg6m.fsf@gnu.org> References: <20170608083935.izw747zaetkaxv4o@abyayala> <87poamv2i7.fsf@gnu.org> <87375jchbu.fsf@gnu.org> <87shdituzk.fsf@elephly.net> <87vaiebk8d.fsf@gnu.org> <87lgjatgn7.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eEW4n-00073o-7Y for bug-guix@gnu.org; Tue, 14 Nov 2017 02:56:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eEW4i-0007LI-BW for bug-guix@gnu.org; Tue, 14 Nov 2017 02:56:09 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58808) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eEW4i-0007Kv-7V for bug-guix@gnu.org; Tue, 14 Nov 2017 02:56:04 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87lgjatgn7.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 13 Nov 2017 15:09:00 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 27284@debbugs.gnu.org Morning! Ricardo Wurmus skribis: > Ludovic Court=C3=A8s writes: [...] >> So what are the options? If we get a bug-fix for Guile=E2=80=99s compil= er >> 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=E2=80=99s 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=E2=80=99t get around distributing pac= kage > definitions. If we can get a fix for Guile soon that=E2=80=99s great, bu= t 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=E2=80=99ll leave that task for someone else, because I don=E2=80= =99t think I > can do more than haskell.scm today. I=E2=80=99ve moved 129 packages from python.scm to python-web.scm: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3D1b2f753d9c73a5431= ec1f5510449c480debf80ce There are still 863 left in python.scm, and it would be good to be at 400=E2=80=93500 max. I=E2=80=99ll see if I can do python-crypto or python-= check today. Thank you for your work on haskell.scm and perl.scm! Ludo=E2=80=99.