unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: Andy Wingo <wingo@pobox.com>, guix-devel@gnu.org
Subject: Making service values transparent
Date: Sun, 05 Apr 2015 22:33:43 +0200	[thread overview]
Message-ID: <871tjyco2g.fsf_-_@gnu.org> (raw)
In-Reply-To: <87r3ryfwvi.fsf@fsf.org> (David Thompson's message of "Sun, 05 Apr 2015 10:55:13 -0400")

David Thompson <dthompson2@worcester.edu> skribis:

> Andy Wingo <wingo@pobox.com> writes:
>
>> Two patches attached.
>>
>> Unfortunately to use this you need to expand out %base-services to add
>> upower to the udev-service form.  Also you need the upower-service,
>> obviously, and upower needs to be added to the dbus-service form as
>> well.
>
> This isn't the first time I've seen people expanding out %base-services,
> and I was also planning to do so for my OS config.  I wonder if we
> should create a 'make-base-services' procedure that accomodates the
> common tweaks to the %base-services list: the MOTD, the list of packages
> for dbus-service, etc.

This must be fixed, basically by making the return value of the
foo-service procedures transparent and amenable to customization,
filtering, etc.

Now that we have extensible gexps, I think we may be able to
“demonadify” those service procedures, by adding declarative forms
corresponding to ‘text-file*’ and co. (just like ‘local-file’ is the
declarative equivalent of the ‘interned-file’ procedure.)

I’m not yet sure this is the right thing, but it’s appealing.

Thoughts?

Ludo’.

  reply	other threads:[~2015-04-05 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 19:56 [PATCH] Add upower Andy Wingo
2015-04-05 14:55 ` David Thompson
2015-04-05 20:33   ` Ludovic Courtès [this message]
2015-04-12 21:01   ` Ludovic Courtès
2015-04-05 15:07 ` Mark H Weaver
2015-04-12 22:05 ` 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=871tjyco2g.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=wingo@pobox.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 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).