[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Service refactoring
From: |
Andy Wingo |
Subject: |
Re: Service refactoring |
Date: |
Tue, 08 Sep 2015 10:47:34 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
On Sun 06 Sep 2015 23:23, address@hidden (Ludovic Courtès) writes:
> Service types and their “extends” relations form a DAG
I am not sure how much ordering matters. The reason is that the
"extends" relations actually proceed from packages associated with a
service, not the service itself. It's enough to know the set of
services and their associated extends; ordering does not appear to be
important. Of course we could do a topological sort on services for
some other reason, but we don't actually need to for these purposes.
I think a two-phase configuration can work: one, in which we specify
services like this:
(operating-system
...
(services SERVICES))
and a second in which the services are "finalized". Finalization is a
monadic procedure of type SERVICE SERVICES -> SERVICE. Finalization is
where e.g. udev would grovel the SERVICES to collect all udev extends.
Andy
- [PATCHES] Get elogind-service working as intended, Mark H Weaver, 2015/09/03
- Re: Service refactoring, Ludovic Courtès, 2015/09/20
- Re: Service refactoring, Andy Wingo, 2015/09/21
- Re: Service refactoring, Ludovic Courtès, 2015/09/21
- Re: Service refactoring, Thompson, David, 2015/09/23
- Re: Service refactoring, Ludovic Courtès, 2015/09/24