From: Jeremiah@pdp10.guru
To: pjotr.public12@thebird.nl
Cc: guix-devel@gnu.org
Subject: Re: Creating a reliable bootstrap for building from source
Date: Sun, 14 May 2017 20:11:51 -0400 [thread overview]
Message-ID: <877f1jugfs.fsf@ITSx00.pdp10.guru> (raw)
> What you are trying to do is even more heroic - bootstrapping all of
> guix :)
The real heros are those that check our work, report bugs and give us
insight into solving our most difficult problems.
And we LOVE patches and pull requests ;-D
> What I want is achievable, simply have the build system as a tested
> binary available. A tested builder package that is know to work
> against the current tree. We pretty much have it, it is only not
> formalized and tested on the build farm
If what you want is achievable and going to help, then please do it.
No need to ask, we always love people who take time to make things
better.
-Jeremiah
next reply other threads:[~2017-05-15 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 0:11 Jeremiah [this message]
-- 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-03-15 16:13 Ready for Guile 2.2! Ludovic Courtès
2017-04-22 22:34 ` ‘guix pull’ vs. transition to Guile 2.2 Ludovic Courtès
2017-05-09 21:22 ` Heads-up: " Ludovic Courtès
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
2017-05-17 7:47 ` Pjotr Prins
2017-05-19 8:58 ` Ludovic Courtès
2017-05-17 7:52 ` Pjotr Prins
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=877f1jugfs.fsf@ITSx00.pdp10.guru \
--to=jeremiah@pdp10.guru \
--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).