From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Python-build-system does not honour phases Date: Tue, 10 Sep 2013 10:26:55 +0200 Message-ID: <20130910082655.GA8621@debian> References: <20130907222607.GA28990@debian> <87hadtfzk4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55082) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJJI3-0006M0-G4 for guix-devel@gnu.org; Tue, 10 Sep 2013 04:27:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VJJHw-0000dp-5x for guix-devel@gnu.org; Tue, 10 Sep 2013 04:27:15 -0400 Content-Disposition: inline In-Reply-To: <87hadtfzk4.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?iso-8859-15?Q?Court=E8s?= Cc: guix-devel@gnu.org On Mon, Sep 09, 2013 at 11:35:55PM +0200, Ludovic Courtès wrote: > The problem is that both the gnu-build-system and the > python-build-system were getting imported, and both export a > ‘%standard-phases’. That is what I thought. I tried to add a #:use-module ((guix build-system gnu) #:select (gnu-build-system)) but that was not enough. > The fix is to use only python-build-system: That also does not seem to work. I split out the packages into two modules, python for the python binaries that use gnu-build-system, and python-modules for the packages using python-build-system. The same error occurs, (alist-replace %standard-build-system) ends up with the configure from gnu-build-system. Could it have something to do with the way %standard-phases of python are derived from those of gnu? Or that code is quoted and executed in a different environment from where it is written? Maybe we should try to use a variable name %python-standard-phases instead. Andreas