From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:55617) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jC6mt-0004mH-8X for guix-patches@gnu.org; Wed, 11 Mar 2020 15:13:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jC6ms-0003jq-A3 for guix-patches@gnu.org; Wed, 11 Mar 2020 15:13:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49564) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jC6ms-0003jh-4V for guix-patches@gnu.org; Wed, 11 Mar 2020 15:13:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jC6mr-0007Y9-Vr for guix-patches@gnu.org; Wed, 11 Mar 2020 15:13:01 -0400 Subject: [bug#39966] [PATCH 0/3] add compiledb Resent-Message-ID: Date: Wed, 11 Mar 2020 15:12:07 -0400 From: Leo Famulari Message-ID: <20200311191207.GD26593@jasmine.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Yuval Kogman Cc: 39966@debbugs.gnu.org On Sat, Mar 07, 2020 at 03:30:20AM +0000, Yuval Kogman wrote: > This patchset adds the compiledb, which is similar to bear. > > FWIW, I was having trouble using bear (seems to segfault during ld > preload, before main(), so I was unable to generate a stacktrace). > > Yuval Kogman (3): > gnu: Add python-bashlex. > gnu: Add python-shutilwhich. > gnu: Add python-compiledb. Thanks! Unless you specifically need the Python 2 variants of bashlex and shutilwhich, we can omit them. We are not adding Python 2 package variants by default anymore. I wonder about shutilwhich, which is a backport of a feature from Python 3.3. We are using Python 3.7 so this should not be necessary, right? Does compiledb require it specifically? Can you send a revised patch series addressing this feedback? And when you do, please make sure to add copyright lines for yourself to the files you edit, and generate the patches using `git format-patch`, or even `git send-email`, sending the mail to this bug report address.