bug-mes
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What is a "mes-compatible" Scheme?


From: Jan Nieuwenhuizen
Subject: Re: What is a "mes-compatible" Scheme?
Date: Wed, 08 Sep 2021 19:17:54 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Sage Gerard writes:

Hello Sage,

> I am trying to build an auditable OS like Guix system does. I wrote a
> more generalized dependency management model called Xiden that offers
> many of the same benefits as Guix, but differs in some ways.

Interesting!

> I use Guix System to indirectly adopt the benefits of Mes for now, but
> I would prefer to build directly on top of Mes to learn more about
> GNU/Linux and OS Dev. I simply prefer a Racket/Xiden stack, and
> getting them working on top of an auditable binary seed would be
> fantastic practice for my education. If you can help me use Mes to
> learn in this way, then I'll find a way to make it easier for others
> to do the same. My hope is that this will create more channels for you
> to recruit volunteers, since I think Mes can become a component in
> more operating system projects.

Yes, that makes sense.

> Could you please point me to some prerequisite reading that the manual
> does not already make clear? I still don't quite understand how
> control moves from stage0 to Mes, or from Mes to a higher level
> technology. Once I get an idea, I should end up more self-sufficient.

I sent an outline of this to gnu-misc-discuss a while ago

    https://lists.gnu.org/archive/html/gnu-misc-discuss/2021-04/msg00057.html

that may answer some of your questions.  In short: use the 'wip-m2'
branch of Mes like it's done in the 'wip-full-source-bootstrap' branch
in Guix.  You should not need Guile at all.

> Thank you for Mes. It's fascinating work.

That is always very nice to hear,
Greetings,
Janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com



reply via email to

[Prev in Thread] Current Thread [Next in Thread]