From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36074) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVhGN-0001z2-Q4 for guix-patches@gnu.org; Sun, 31 Dec 2017 12:19:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eVhGI-0005Pd-Rf for guix-patches@gnu.org; Sun, 31 Dec 2017 12:19:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50264) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eVhGI-0005PN-Nn for guix-patches@gnu.org; Sun, 31 Dec 2017 12:19:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eVhGI-0002p8-EY for guix-patches@gnu.org; Sun, 31 Dec 2017 12:19:02 -0500 Subject: [bug#29856] [PATCH core-updates] guix: python-build-system: Modify ".py" files in-place. Resent-Message-ID: Date: Sun, 31 Dec 2017 18:17:55 +0100 From: Danny Milosavljevic Message-ID: <20171231181755.7fe64e7e@scratchpost.org> In-Reply-To: <87d12vaqk9.fsf@fastmail.com> References: <20171226122105.19156-1-dannym@scratchpost.org> <20171226191013.GE1413@jasmine.lan> <20171227012326.5aa8a762@scratchpost.org> <87d12vaqk9.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Marius Bakke Cc: 29856@debbugs.gnu.org Hi Marius, On Sun, 31 Dec 2017 16:02:30 +0100 Marius Bakke wrote: > I wonder if this will fix . "meson" is not > installed with a .py extension That bugreport sounds as if the searched-for program is "meson.py". But I tried to install meson while having 29856 applied. Doesn't work. >, but I guess we can call wrap-program* on it. If you made sure the original wrapping thing didn't run, yeah. That's why I did such an intrusive fix in the first place. > Would it work to peek at the shebang instead of the file extension? Probably, but I wanted it to be dead easy for core-updates. Not sure whether, if we examined the content, there would be any false positives, empty files, dangling symlinks, special files etc which would need special handling. Every change there rebuilds for several hours on my machine, so I'd like a sure-to-work block even when testing :)