[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Defining user services in Guix.
From: |
Ludovic Courtès |
Subject: |
Re: Defining user services in Guix. |
Date: |
Tue, 02 May 2017 12:02:52 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hello Mathieu,
Mathieu Othacehe <address@hidden> skribis:
>> Agreed. A ‘guix user’ tool (or similar) could talk to the user’s
>> Shepherd instance to upgrade user services like
>> ‘upgrade-shepherd-services’ does in (guix scripts system).
>
> With the attached patch, it is possibe to use (gnu services herd) to
> interact with a user shepherd instance.
>
> For instance :
>
> (use-modules (gnu services herd))
> (parameterize
> ((%shepherd-socket-file "/home/mathieu/.config/shepherd/run/socket"))
> (current-services))
>
>
> Which returns :
>
> $1 = (#<<live-service> provision: (redshift) requirement: () running: 3632>
> #<<live-service> provision: (root shepherd) requirement: () running: #t>)
>
> Based on that, I'll try to define a guix user command to upgrade user
> services if it is ok for everyone :).
Neat, sounds like a good plan!
Could you create an account on Savannah, add the OpenPGP public key
you’ll use to sign commits there, and let us know when you’re done with
a signed message? Looks like we should be able to increase the
bandwidth. :-)
Thanks,
Ludo’.
- Re: Defining user services in Guix.,
Ludovic Courtès <=