[artix-general] [s6] new adminsv + [new?] network bundle + bundles in general

[Javier]

Hello !

I noticed last week or early this week s6 users got new stuff:

> /etc/s6/adminsv

Inside you can find specific additional configuration for the:

> /etc/s6/rc.local

oneshot, like:

> % ls /etc/s6/adminsv/rc-local/                                                                                                                                                                                                     
> dependencies  down  type  up

An nice but short description about it was added to the wiki:

> directory for custom user services as well as script packages from Artix that allow for editing

Which seems in line with that new *adminsv* including oneshot configuration for rc.local.  However it includes what seems a new bundle as well?

> % ls /etc/s6/adminsv/network/
> contents  type
> % cat /etc/s6/adminsv/network/type                                                                                                                                                                                                 
> bundle
> % cat /etc/s6/adminsv/network/contents 
> %

So it seems we have a new bundle called *network*.  Is it meant only for non artix provided <package>-s6 oneshots and services. given it's under **/etc/s6/adminsv**?  Or is meant to include everything depending on *networking* somehow?  Should we, for example, move freshclam, dhcpcd, and other *netowrw* oneshots/services to the new bundle?

So far, after installing an artix provided <package>-s6 package, then I proceed to add its included oneshot/service to the default bundle.  I have applied no exception to this procedure, unless when seeing a message log when installing, and some *filesystem* related ones, which I've noticed they are automatically bundled to boot most of the time or default.  This was requirement some time ago, when I installed artix, however the wiki seems to suggest different:

> *Note*: the *-s6 packages in Artix that are an optional dependency of s6-scripts install themselves inside the boot bundle. They do not need to be enabled manually or added to any other bundle

This seems to kill the procedure I always apply.  To be honest, it's not that often that I add new <package>-s6 packages, but I'd like to be certain.  Should I stop applying my procedure moving forward?  And trust whether the <package>-s6 packages' PKGBUILDs include some magic to automatically add their oneshots/services to the corresponding bundle (whether boot or default), or there's a pacman magic hook for that same purpose?  If this is the case, perhaps my questions about moving *network* related oneshots/services from *default* to *network* makes no sense at all, since artix somehow places them in the right bundle to begin with...  I can't tell for sure, or better said, I haven't spent the time to confirm every <package>-s6 package I install, automatically gets into a bundle, since I apply the procedure I mentioned instead, :).

Is there a PKGBUILD of reference for writing <package>-s6 packages, which oneshots/services get automatically bundled one can take a look at?  Well, if there's some hook to the PKGBUILD, that is, otherwise I'd guess it's a pacman hook...

OK, I think enough questions for a single email thread, :)  Thanks !

-- 
Javier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20211003/414f2845/attachment-0001.sig>