Re: [gentoo-user] Update of systemd-utils failes (OpenRC)

[Eli Schwartz <eschwartz@gentoo.org>]

[-- Attachment #1.1: Type: text/plain, Size: 2939 bytes --]

On 2/8/25 3:56 AM, Matthias Hanft wrote:
> Just the question remains:
> 
>>  U I
>>  - - abi_x86_32                      : 32-bit (x86) libraries
>>  + + acl                             : Add support for Access Control Lists
>>  - - boot                            : Enable systemd-boot (UEFI boot manager)
>>  - - kernel-install                  : Enable kernel-install
>>  + - kmod                            : Enable kernel module loading via sys-apps/kmod
>>  - - python_single_target_python3_10 : Build for Python 3.10 only
>>  - - python_single_target_python3_11 : Build for Python 3.11 only
>>  + + python_single_target_python3_12 : Build for Python 3.12 only
>>  - - python_single_target_python3_13 : Build for Python 3.13 only
>>  - - secureboot                      : Automatically sign efi executables using user specified key
>>  - - sysusers                        : Enable systemd-sysusers
>>  - - test                            : Enable dependencies and/or preparations necessary to run tests (usually
>>                                        controlled by FEATURES=test but can be toggled independently)
>>  + - tmpfiles                        : Enable systemd-tmpfiles
>>  + - udev                            : Enable systemd-udev (userspace device manager)
>>  - - ukify                           : Enable systemd-ukify
> 
> With the update installed, the USE flags kmod, tmpfiles and udev changed
> from "off" to "on".


The original 2022 addition of the systemd-utils package defaulted kmod
and tmpfiles and udev to "on". In order to install it with those USE
flags toggled "off" you would have had to locally set that in your
package.use -- your reasons for doing so are best known by yourself. :)

Those are decent defaults as you really want to have a tmpfiles.d
processor of some sort, and a udev daemon, and the versions that were
carved out of the systemd project and provided as standalone tools in
"systemd-utils" are currently the only packaged versions of either one
in ::gentoo (as the alternative for e.g. udev was just an outdated and
unmaintained fork of systemd, and the alternative for tmpfiles was an
insecure and abandoned project).

It leaves open the question, which other packages did you use to satisfy
the dependencies of:

virtual/tmpfiles
virtual/udev


> Is this important, do I have to worry, or can I just
> ignore it (because there's no impact at all without systemd?


As Michael noted, systemd-utils exists to be a small collection of a few
tools extracted from the systemd source code -- using the systemd-utils
package at all, implies you aren't using systemd (in fact, systemd-utils
will conflict with systemd! portage will not let you install systemd, if
systemd-utils is currently installed), and thus per definition the
systemd-utils package can't have any cause for concern with regard to
systemd.



-- 
Eli Schwartz

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]