Changeset b980f67

Timestamp:

07/12/2023 07:38:38 PM (11 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

12.0, 12.1, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal

Children:

ea781cd

Parents:

b1a8c0e8

git-author:

Xi Ruoyao <xry111@…> (07/12/2023 07:32:45 PM)

git-committer:

Xi Ruoyao <xry111@…> (07/12/2023 07:38:38 PM)

Message:

elogind: Fix the desc for -Dcgroup-controller

The value of this switch only makes a difference with cgroupv1. But we
are using Linux 6.x, and elogind is built with
-Ddefault_hierarchy=unified (the default), so it actually uses cgroupv2
and it seems we don't really need this switch.

But after a closer look at the building system I realized if the kernel
is not built with CONFIG_CGROUPS enabled (for example in a chroot
environment where the host does not enable this), the building system
will refuse to build the package w/o an explicit setting here. So
update the description.

File:

• general/sysutils/elogind.xml (modified) (1 diff)

general/sysutils/elogind.xml

@@ -210 +210 @@
 
     <para>
-      <parameter>-Dcgroup-controller=elogind</parameter>: This switch ensures
-      that <application>elogind</application> is selected as the cgroup
-      controller, even if booted with another running cgroup controller.
+      <parameter>-Dcgroup-controller=elogind</parameter>: This switch is
+      necessary to build this package when the kernel is not built with
+      <option>CONFIG_CGROUPS</option> enabled.  Note that
+      <application>elogind</application> strictly needs
+      a kernel with <option>CONFIG_CGROUPS</option> enabled at runtime,
+      but this switch will allow building the package first.
     </para>