From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Creating a reliable bootstrap for building from source Date: Mon, 15 May 2017 15:28:58 +0200 Message-ID: <87r2zqi6zp.fsf@gnu.org> References: <87bmt28qnm.fsf@gnu.org> <87k26chy16.fsf@gnu.org> <87y3u5wwsi.fsf_-_@gnu.org> <20170514135041.GA29369@thebird.nl> <20170514153506.GA29953@thebird.nl> <20170514161342.GA30265@thebird.nl> <87efvr769a.fsf@gnu.org> <20170514172927.GA31005@thebird.nl> <20170514183014.GA31243@thebird.nl> <87shk7qg4p.fsf@gnu.org> <20170515073506.GA1125@thebird.nl> 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]:42585) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dAG3q-0003xl-Qr for guix-devel@gnu.org; Mon, 15 May 2017 09:29:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dAG3n-0002hI-Lc for guix-devel@gnu.org; Mon, 15 May 2017 09:29:18 -0400 In-Reply-To: <20170515073506.GA1125@thebird.nl> (Pjotr Prins's message of "Mon, 15 May 2017 09:35:06 +0200") 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" To: Pjotr Prins Cc: guix-devel Pjotr Prins skribis: > On Sun, May 14, 2017 at 11:32:06PM +0200, Ludovic Court??s wrote: >> Pjotr Prins skribis: >>=20 >> > The combination of 'guix pull' held a promise, were it not that pull is >> > also iffy. Probably for pretty much the same reason. >> > >> > The bootstrap+configure scripts try to work that, but actually >> > address a wider case. I.e. people who want to bootstrap in Debian etc. >> > I don't think we need al that. I write Makefile.guix for my projects >> > and they tend to be simple! Once you can assume Guix is there life >> > gets simple as a developer - except when you try to bootstrap :0 >> > >> > The instruction I would like to write for others is: >> > >> > 1. Install the latest bootstrap-guix-from-source package after a guix = pull >> > 2. git clone guix && cd guix >> > 3. run make -f Makefile.guix=20=20 >> > >> > (no configure is needed in guix!) >> > >> > 4. ./pre-inst guix etc. etc. >>=20 >> I think there are two very different use cases. >>=20 >> As a user I want something like 'apt-get update', which is what 'guix >> pull' tries to do. > > Sure. But from my previous E-mail you can see we are effectively using > pull to bootstrap the source tree build. Sure. >> For Guix developers, I think it's reasonable to have a traditional GNU >> build system. After all, Guix is also a regular software package that >> people can build from source with './configure && make && make install'. > > My point is that we can simplify. I like simple. Simple is good. > > We can have both the configure and a simple Makefile.guix option. That > is what I do with my projects. > > We do not need bootstrap, autoconf and configure on a running Guix > system. We do need it for other distributions. I agree. build-aux/build-self.scm, which is what =E2=80=98guix pull=E2=80= =99 runs to build Guix, is close to what you=E2=80=99re suggesting, IIUC: a pure-Guile = build script. WDYT? Ludo=E2=80=99.