From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Creating a reliable bootstrap for building from source
Date: Mon, 15 May 2017 15:28:58 +0200 [thread overview]
Message-ID: <87r2zqi6zp.fsf@gnu.org> (raw)
In-Reply-To: <20170515073506.GA1125@thebird.nl> (Pjotr Prins's message of "Mon, 15 May 2017 09:35:06 +0200")
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> On Sun, May 14, 2017 at 11:32:06PM +0200, Ludovic Court??s wrote:
>> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>>
>> > 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
>> >
>> > (no configure is needed in guix!)
>> >
>> > 4. ./pre-inst guix etc. etc.
>>
>> I think there are two very different use cases.
>>
>> 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 ‘guix pull’ runs to
build Guix, is close to what you’re suggesting, IIUC: a pure-Guile build
script. WDYT?
Ludo’.
next prev parent reply other threads:[~2017-05-15 13:29 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 16:13 Ready for Guile 2.2! Ludovic Courtès
2017-03-15 20:33 ` Pjotr Prins
2017-03-15 20:41 ` Ludovic Courtès
2017-04-20 12:35 ` Ludovic Courtès
2017-04-20 13:10 ` Andy Wingo
2017-04-20 15:21 ` Maxim Cournoyer
2017-04-21 16:05 ` Joshua Branson
2017-04-22 22:20 ` Ludovic Courtès
2017-04-21 21:03 ` Ludovic Courtès
2017-04-24 1:31 ` Maxim Cournoyer
2017-04-21 21:14 ` Ludovic Courtès
2017-03-31 16:34 ` Ludovic Courtès
2017-04-22 22:34 ` ‘guix pull’ vs. transition to Guile 2.2 Ludovic Courtès
2017-04-23 14:09 ` Jan Nieuwenhuizen
2017-04-27 13:25 ` Ludovic Courtès
2017-05-09 21:22 ` Heads-up: " Ludovic Courtès
2017-05-09 22:26 ` myglc2
2017-05-10 12:05 ` Ludovic Courtès
2017-05-10 17:11 ` myglc2
2017-05-11 0:40 ` myglc2
2017-05-11 8:29 ` Ludovic Courtès
2017-05-11 8:50 ` Vincent Legoll
2017-05-11 20:53 ` Ludovic Courtès
2017-05-11 11:53 ` myglc2
2017-05-11 17:48 ` ng0
2017-05-11 18:17 ` ng0
2017-05-11 20:49 ` Adonay Felipe Nogueira
2017-05-12 8:11 ` Chris Marusich
2017-05-18 12:32 ` ng0
2017-05-14 13:50 ` Pjotr Prins
2017-05-14 15:35 ` Pjotr Prins
2017-05-14 16:13 ` Pjotr Prins
2017-05-14 16:28 ` Jan Nieuwenhuizen
2017-05-14 17:29 ` pjotr.public12
2017-05-14 18:30 ` Creating a reliable bootstrap for building from source Pjotr Prins
2017-05-14 21:32 ` Ludovic Courtès
2017-05-15 1:20 ` David Pirotte
2017-05-15 13:27 ` Ludovic Courtès
2017-05-15 7:35 ` Pjotr Prins
2017-05-15 13:28 ` Ludovic Courtès [this message]
2017-05-17 7:47 ` Pjotr Prins
2017-05-19 8:58 ` Ludovic Courtès
2017-05-17 7:52 ` Pjotr Prins
2017-05-14 21:28 ` Heads-up: transition to Guile 2.2 Ludovic Courtès
2017-05-15 7:26 ` Pjotr Prins
2017-05-15 15:48 ` Ludovic Courtès
2017-05-15 20:24 ` Rethinking guix pull [was Re: Heads-up: transition to Guile 2.2] myglc2
2017-05-16 15:55 ` Ricardo Wurmus
2017-05-16 20:56 ` Maxim Cournoyer
2017-05-18 13:54 ` Katherine Cox-Buday
2017-05-18 15:08 ` Ludovic Courtès
2017-05-17 12:45 ` Ludovic Courtès
2017-05-17 17:54 ` myglc2
2017-05-17 16:06 ` myglc2
2017-05-17 17:46 ` myglc2
2017-05-17 23:45 ` Leo Famulari
2017-05-12 5:41 ` ‘guix pull’ vs. transition to Guile 2.2 Chris Marusich
-- strict thread matches above, loose matches on Subject: below --
2017-05-14 19:54 Creating a reliable bootstrap for building from source Jeremiah
2017-05-14 21:17 ` Pjotr Prins
2017-05-15 0:11 Jeremiah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2zqi6zp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).