From: Ricardo Wurmus <rekado@elephly.net>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: reconfiguring
Date: Tue, 13 Feb 2018 21:33:49 +0100 [thread overview]
Message-ID: <87eflok4sy.fsf@elephly.net> (raw)
In-Reply-To: <87sha4wvrk.fsf@zancanaro.id.au>
Carlo Zancanaro <carlo@zancanaro.id.au> writes:
> On Tue, Feb 13 2018, Ricardo Wurmus wrote:
>> That’s a misunderstanding. All of the things in the “services”
>> field of
>> your operating-system configuration are “system services”, so
>> all of
>> them get updated.
>
> Should we think about changing the name for "system services"? The
> confusion with Shepherd services seems really easy to make. The
> Wikipedia article for GuixSD makes the same mistake, but I haven't
> had the chance to fix it yet. Maybe we should call them "system
> extensions", or "mixins", or something like that?
I would very much like to find a new term for them, because usually the
second thing I say about system services is that the naming is
unfortunate and collides with what people think is a shepherd service.
I’m not fond of “mixins” (this reminds me of the “traits”-like concept
in Ruby classes), nor do I really like “system extensions”, but I do
think that avoiding the naming conflict would be worth a bike-shed
discussion :)
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2018-02-13 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 15:35 reconfiguring Catonano
2018-02-13 18:25 ` reconfiguring Ricardo Wurmus
2018-02-13 19:03 ` reconfiguring Leo Famulari
2018-02-13 19:11 ` reconfiguring Ricardo Wurmus
2018-02-13 19:18 ` reconfiguring Carlo Zancanaro
2018-02-13 19:22 ` reconfiguring Leo Famulari
2018-02-13 20:32 ` reconfiguring Andreas Enge
2018-02-13 23:32 ` reconfiguring myglc2
2018-02-14 7:49 ` reconfiguring Ricardo Wurmus
2018-02-13 19:10 ` reconfiguring Carlo Zancanaro
2018-02-13 20:33 ` Ricardo Wurmus [this message]
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=87eflok4sy.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=carlo@zancanaro.id.au \
--cc=help-guix@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.
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).