Re: s6-rc: "situation-dependent" dependencies.d

Am Sa, Mai 16, 2026 am 02:02:56 -0300 schrieb Guillermo:
>Hello!
>
>El sáb, 16 may 2026 a las 13:09, Hoël Bézier escribió:
>>
>> For this kind of things, instead of a localmount service, I’d use a localmount
>> bundle, whose contents I would change depending on my use case.
>
>Hmm, not sure how one would use bundles for the described cases, but
>changing the contents of bundles also means changing their definitions
>(contents of directory 'contents.d') in a service store, unless you
>are thinking of the special case of using s6-rc-bundle on a database
>that is live. Doesn't sound too different to just adjusting
>'dependencies.d' contents, if one is already accepting the idea that
>service stores must be touched...

Yeah, I’m talking about touching service stores, though you should be touching 
the one in /etc, instead of the one in /usr (that I assume is the one provided 
by your distribution). Also, by changing a bundles contents, you can keep your 
changes localized to one place, instead of changing dependencies of all 
services that require mount points (and there can be a whole lot of them).
>
>> But since s6-frontend doesn’t handle bundles, [...]
>
>What do you mean by this? It looks like it does to me... You create
>bundle definitions in a service store and 's6 repository sync' will
>add them to the repository.

I mean that s6 live start/stop does not take bundle as arguments. `s6 repo sync` 
only creates symlinks, the rest of the handling is done by s6-rc, which does 
handle bundles. I’m also not sure whether s6 set enable/disable takes bundles 
as arguments, I’d have to check.

Though I think Laurent’s aware of this (it has been reported on the irc channel) 
and has been working on it.