From: "Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: RE: bootstrap integration strategies
Date: Mon, 16 Jul 2018 11:11:46 +0000 [thread overview]
Message-ID: <CY1PR09MB0811BB6DEDD2BFE83D23BB1AC65D0@CY1PR09MB0811.namprd09.prod.outlook.com> (raw)
In-Reply-To: <87efg7q9jv.fsf@elephly.net>
> I agree. We need to make sure, though, that the Guix build infrastructure doesn’t add more complicated packages to the environment that are not needed.
Especially since those are the varieties that no one wants to be responsible for maintaining.
> Right. We would need to cut out Guile on the build side.
Which would significantly increase system resource requirements, unless we make this a 1 time only cost sort of thing.
> I would love to take a closer look again before merging it.
> Unfortunately, these days I’m a bit short on time as I’m on “vacation”
> with other plans imposed on my schedule.
Ricardo, we love you dearly but please for the love of all that is holy;
Get back to that vacation! *cracks whip* Burnout is a real thing and believe me when I say bootstrapping is a marathon
Jeremiah Orians
Cell phone: (517) 896-2948
next prev parent reply other threads:[~2018-07-16 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 12:16 bootstrap integration strategies Orians, Jeremiah (DTMB)
2018-07-12 16:15 ` Ludovic Courtès
2018-07-12 17:10 ` Orians, Jeremiah (DTMB)
2018-07-12 17:40 ` Jan Nieuwenhuizen
2018-07-12 19:52 ` Jan Nieuwenhuizen
2018-07-13 12:20 ` Ludovic Courtès
2018-07-13 14:19 ` Jan Nieuwenhuizen
2018-07-13 18:23 ` Ricardo Wurmus
2018-07-16 11:11 ` Orians, Jeremiah (DTMB) [this message]
2018-07-16 21:37 ` Brett Gilio
2018-07-12 17:44 ` Jan Nieuwenhuizen
-- strict thread matches above, loose matches on Subject: below --
2018-07-09 20:55 Jan Nieuwenhuizen
2018-07-11 13:13 ` 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
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=CY1PR09MB0811BB6DEDD2BFE83D23BB1AC65D0@CY1PR09MB0811.namprd09.prod.outlook.com \
--to=oriansj@michigan.gov \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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).