all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: GOOPS-less Shepherd
Date: Thu, 06 Apr 2023 22:16:31 +0200	[thread overview]
Message-ID: <87r0swhilc.fsf@inria.fr> (raw)

Hello!

I’d like to release the Shepherd 0.10.0 in a few weeks at most, with the
hope that it’ll be the last stable series before 1.0, which would be
released in a few months.

As part of this, I’d like to clean up the API, which includes removing
the dependency on GOOPS.  The Shepherd had been using GOOPS from the
start but for no particular reason: there’s no inheritance and only a
couple of cases of method overloading.

I started that work, which mostly involves renaming things like
accessors following typical Scheme conventions:

  https://git.savannah.gnu.org/cgit/shepherd.git/log/?h=wip-goopsless

I imagine the following deprecation scenario:

  • 0.10.x would still support GOOPS, as in (make <service> …), but
    that would be deprecated in favor of a more Schemey (service …)
    form.  Under the hood it’s still GOOPS.

  • 1.0.x would no longer use GOOPS at all.  We could provide a ‘make’
    macro so that (make <service> …) would still kinda work.

What’s at stake, mostly, is the ability to reconfigure a long-running
shepherd instance.  Once 1.0.x is in Guix, ‘guix system reconfigure’
will most likely fail to upgrade services on a pre-0.10.x shepherd:
users will have to reboot.

Thoughts?

Ludo’.


             reply	other threads:[~2023-04-06 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 20:16 Ludovic Courtès [this message]
2023-04-07 21:21 ` GOOPS-less Shepherd 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0swhilc.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    /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.