From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Svante Signell <svante.signell@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [Proposal] The Formal Methods in GNU Guix Working Group
Date: Wed, 12 Feb 2020 15:48:46 +0100 [thread overview]
Message-ID: <87tv3vj1yp.fsf@gnu.org> (raw)
In-Reply-To: <46c59db847cdeb378d712af99dfe0940a583f68e.camel@gmail.com> (Svante Signell's message of "Wed, 12 Feb 2020 15:38:27 +0100")
Svante Signell writes:
> On Wed, 2020-02-12 at 15:16 +0100, zimoun wrote:
>> Dear,
>>
>> On Wed, 12 Feb 2020 at 13:03, Orians, Jeremiah (DTMB)
>> <OriansJ@michigan.gov> wrote:
>>
>> > We also have a scheme bootstrappable from nothing written in C
>> > https://github.com/oriansj/mes-m2
>> > https://github.com/oriansj/mescc-tools-seed
>>
>> The term "nothing" is mitigated; i.e. "nothing" means: a booted system
>> running a (linux) kernel. Right?
>
> I do also suspect that mes* is only for Linux so far. Any plans for Hurd?
Your suspicion is somewhat correct. GNU Mes v0.22 added initial support
for the Hurd, and introduced a FreeBSD scaffold. Support for the Hurd
has always been the plan, see the Guix ROADMAP or the manual
(https://guix.gnu.org/manual/en/html_node/operating_002dsystem-Reference.html#FOOT23).
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-12 14:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 12:02 [Proposal] The Formal Methods in GNU Guix Working Group Orians, Jeremiah (DTMB)
2020-02-12 14:16 ` zimoun
2020-02-12 14:38 ` Svante Signell
2020-02-12 14:48 ` Jan Nieuwenhuizen [this message]
2020-02-12 20:59 ` Bengt Richter
2020-02-13 12:13 ` Orians, Jeremiah (DTMB)
2020-02-13 12:07 ` Orians, Jeremiah (DTMB)
2020-02-15 16:10 ` zimoun
2020-02-18 11:17 ` Orians, Jeremiah (DTMB)
2020-02-21 14:47 ` zimoun
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 19:17 Alexandru-Sergiu Marton
2019-12-16 0:59 Brett Gilio
2019-12-16 8:47 ` Julien Lepiller
2019-12-16 9:22 ` Julien Lepiller
2019-12-17 3:29 ` Brett Gilio
2019-12-27 18:56 ` Ludovic Courtès
2019-12-27 22:33 ` Brett Gilio
2019-12-27 23:37 ` Ludovic Courtès
2019-12-28 2:59 ` Brett Gilio
2019-12-30 21:34 ` Ludovic Courtès
2019-12-31 10:17 ` Brett Gilio
2020-01-02 22:11 ` Ludovic Courtès
2020-01-03 23:49 ` Amin Bandali
2020-01-15 21:59 ` Ludovic Courtès
2020-01-13 19:27 ` Maxim Cournoyer
2019-12-28 7:20 ` Amin Bandali
2019-12-28 11:28 ` Vicente Eduardo
2019-12-29 8:09 ` Jan Nieuwenhuizen
2019-12-17 3:27 ` Brett Gilio
2019-12-16 19:46 ` zimoun
2019-12-16 20:10 ` Julien Lepiller
2019-12-17 3:40 ` Brett Gilio
2019-12-27 23:56 ` Ludovic Courtès
2019-12-28 2:55 ` Brett Gilio
2019-12-17 3:38 ` Brett Gilio
2019-12-16 23:04 ` Jack Hill
2019-12-17 1:33 ` John Soo
2019-12-17 3:49 ` Brett Gilio
2019-12-17 3:48 ` Brett Gilio
2019-12-21 6:48 ` Amin Bandali
2019-12-21 23:59 ` Brett Gilio
2019-12-28 0:02 ` Ludovic Courtès
2019-12-27 23:54 ` Ludovic Courtès
2019-12-28 3:06 ` Brett Gilio
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=87tv3vj1yp.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=svante.signell@gmail.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.