From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Timothy Sample <samplet@ngyro.com>, 38390@debbugs.gnu.org
Subject: [bug#38390] [bug #38390] Building bootstrap Gash and Gash-Utils
Date: Thu, 06 Feb 2020 23:58:28 +0100 [thread overview]
Message-ID: <87ftfn492j.fsf@gnu.org> (raw)
In-Reply-To: <87imkklnwe.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 05 Feb 2020 22:33:53 +0100")
Ludovic Courtès writes:
Hello!
I have rebased wip-bootstrap on core-updates that include your
commencements updates.
With your explanations on irc and studying your patch, I was able to
keep using your cleanups and do without the most ugly 'setenv stages.
So, wip-bootstrap on savannah is reset once again.
> Timothy Sample <samplet@ngyro.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>> I would be happy to do that. It’s nice having everything in one place,
>> but having a bootstrap build system would certainly make the packages
>> clearer. I suppose it could also get rid of the implicit inputs for us
>> and use “%bootstrap-guile” by default.
>
> I doesn’t have to be a full-blown build system, because there might be
> as much boilerplate as actual code, but simply moving the definitions of
> phases in a separate file could help keep commencement.scm clear.
>
>>> I guess the only thing that remains to be done is changing the temporary
>>> URLs to the self-extracting script & co., right?
>>
>> Yup. I’ll release both packages soon.
>
> Great, thank you!
Yes, that's great!
@Timothy: I haven't included your previous patches on `wip-bootstrap',
feel free to push them to wip-bootstrap.
We are getting real close to merging this, I think.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-02-06 22:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 16:38 [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap Jan Nieuwenhuizen
2019-12-01 14:01 ` Ludovic Courtès
2019-12-01 16:25 ` Timothy Sample
2019-12-01 16:55 ` Jan Nieuwenhuizen
2019-12-01 17:14 ` Ludovic Courtès
2019-12-01 17:21 ` Jan Nieuwenhuizen
2019-12-06 6:53 ` Jan Nieuwenhuizen
2019-12-07 22:31 ` Ludovic Courtès
2019-12-11 18:25 ` Jan Nieuwenhuizen
2019-12-15 21:33 ` Ludovic Courtès
2019-12-15 22:39 ` Timothy Sample
2019-12-15 22:45 ` Brett Gilio
2019-12-16 6:34 ` Jan Nieuwenhuizen
2019-12-16 19:28 ` Jan Nieuwenhuizen
2019-12-18 22:55 ` Jan Nieuwenhuizen
2019-12-19 11:08 ` Ludovic Courtès
2020-02-03 17:37 ` [bug#38390] [bug #38390] Building bootstrap Gash and Gash-Utils Timothy Sample
2020-02-05 8:58 ` Ludovic Courtès
2020-02-05 14:32 ` Timothy Sample
2020-02-05 21:33 ` Ludovic Courtès
2020-02-06 22:58 ` Jan Nieuwenhuizen [this message]
2020-02-07 11:00 ` Ludovic Courtès
2020-02-08 17:33 ` Timothy Sample
2020-02-08 22:32 ` Jan Nieuwenhuizen
2020-02-10 2:23 ` Timothy Sample
2020-02-11 13:56 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftfn492j.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=38390@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=samplet@ngyro.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.