From: Ivan Sokolov <ivan-p-sokolov@ya.ru>
To: jbranso@dismail.de
Cc: "Bodertz" <bodertz@gmail.com>, guix-devel@gnu.org
Subject: Re: GOOPS-less Shepherd
Date: Mon, 10 Apr 2023 21:49:15 +0300 [thread overview]
Message-ID: <877cujr2s4.fsf@ya.ru> (raw)
In-Reply-To: <e2bfc96ca385e16d6686798430fbcfb2@dismail.de> (jbranso@dismail.de's message of "Mon, 10 Apr 2023 00:59:49 +0000")
jbranso@dismail.de writes:
> April 8, 2023 8:54 PM, "Ivan Sokolov" <ivan-p-sokolov@ya.ru> wrote:
>
>> Bodertz <bodertz@gmail.com> writes:
>>
>>> I don't have strong feelings either way, and the change won't really
>>> affect me too much, but what benefit is there in breaking things? From
>>> what I understand from your message, users' configs will stop working in
>>> a few months when 1.0.x releases (or with the macro would "kinda work"),
>>> which is at least a short-term con, so what's the long-term benefit of
>>> this change? Is GOOPS so bad a thing to require?
>>
>> If I understand correctly, that will allow Shepherd to run on GNU Mes,
>> a Scheme interpreter written for Guix bootstraping.
>
> So by removing the Shepherd's dependency on GNU Mes, the Guix project
> benefits by simplying its bootstrapping process?
Where did this come from? No, Mes is not a Shepherd's dependency,
please read the quotes again.
next prev parent reply other threads:[~2023-04-10 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 20:16 GOOPS-less Shepherd Ludovic Courtès
2023-04-07 21:21 ` Maxim Cournoyer
2023-04-08 17:25 ` Bodertz
2023-04-09 1:53 ` Ivan Sokolov
2023-04-09 2:37 ` Bodertz
2023-04-10 0:59 ` jbranso
2023-04-10 18:49 ` Ivan Sokolov [this message]
2023-04-13 20:33 ` Ludovic Courtès
2023-04-11 8:15 ` Liliana Marie Prikler
2023-04-13 20:34 ` Ludovic Courtès
2023-04-19 11:44 ` Christine Lemmer-Webber
2023-05-03 20:49 ` 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=877cujr2s4.fsf@ya.ru \
--to=ivan-p-sokolov@ya.ru \
--cc=bodertz@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
/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).