From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Trivial build system Date: Sun, 11 Jan 2015 16:25:09 +0100 Message-ID: <20150111152509.GA23932@debian> References: <20150111151247.GA23839@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAKOF-0003hf-A3 for guix-devel@gnu.org; Sun, 11 Jan 2015 10:25:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YAKOC-0008Gf-4V for guix-devel@gnu.org; Sun, 11 Jan 2015 10:25:19 -0500 Received: from mout.kundenserver.de ([212.227.17.24]:59216) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAKOB-0008Ga-RL for guix-devel@gnu.org; Sun, 11 Jan 2015 10:25:16 -0500 Content-Disposition: inline In-Reply-To: <20150111151247.GA23839@debian> List-Id: "Development of GNU Guix and the GNU System distribution." 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: guix-devel@gnu.org I also wonder if we should not modify the structure of our build system code. Our different build systems end up calling gnu:gnu-build with a list of phases. Could this not be done all the time? And then a build system be defined as a list of phases? For instance, trivial-build-system could be the empty list, or better yet, the list containing 'unpack. Then we could always take the #:phases argument of a package and modify it by adding a phase, for instance; this would be easier than taking a #:build argument and modify it, I think. Andreas