At least "Updates" part is inaccurate.
I think "technically" possible.
Because I don't think FLAVOR is good thing for conflicting things.
XFree86 and Xorg were both monolithic back then; so things were a little easier for people to handle locally admittedly.
So then anything you want to run under Xlibre has to be aware of these mangled names? How's that simpler than FLAVORS?
Have you read the whole post?
Yeah, my bad. Still a whole lot more work than the simple flavorized approach baaz implemented, and still way more friction to someone that just wants to try out Xlibre without spending a bunch of time on it.
diff --git a/x11/plasma6-plasma-desktop/Makefile b/x11/plasma6-plasma-desktop/Makefile
--- a/x11/plasma6-plasma-desktop/Makefile
+++ b/x11/plasma6-plasma-desktop/Makefile
@@ -19,9 +19,7 @@
LIB_DEPENDS= libcanberra.so:audio/libcanberra \
libxkbcommon.so:x11/libxkbcommon \
libxkbfile.so:x11/libxkbfile \
RUN_DEPENDS= noto-emoji>0:x11-fonts/noto-emoji \
- xdg-user-dir:devel/xdg-user-dirs \
- xf86-input-evdev>0:x11-drivers/xf86-input-evdev \
- xf86-input-libinput>0:x11-drivers/xf86-input-libinput
+ xdg-user-dir:devel/xdg-user-dirs
USES= cmake gettext gl gnome kde:6 pkgconfig python qt:6 tar:xz xorg
USE_GL= gl opengl
github.com
Was this cleanup the result of trying to integrate with Xlibre?** The evdev input driver is also depended by plasma-desktop but it has been removed:
kcms/mouse: Remove unused xorg-evdev dependency · KDE/plasma-desktop@b4fe3e9
It's not necessary to access it directly anymore, now that we only expose settings for libinput.
Nope, that commit is from the April of 2024; it is older than XLibre
.
(evdev) to the new one (libinput) and there was no reason to left to support the former.
OK, some more technical stuff.
I have found a better, more elegant solution to the KDE problem.
The entire reason that the KDE x11/plasma6-plasma-desktop port can't be installed alongside xlibre-server is due to its RUNTIME dependency on X.Org drivers:
x11-drivers/xf86-input-libinput
and
x11-drivers/xf86-input-evdev
Now why is there a dependency on these two drivers in the first place?
It is because of the diabolical scheme that was put into place for communicating default values of properties associated with xf86-input-* drivers to the input configuration utilities present in desktop environments.
Instead of a simple, humble text file, the xf86 input drivers generate a C header and a pkgconf file that is then depended on and included by a DE's input configuration tool, and it in turn sets its default values based on the list of "#define"s in these header files.
The things to note:
- This is done for just setting the default values of these configuration utilities.
- All of this is happening during compile time.
The libinput driver is basically the only ** driver whose exported properties are depended on by other ports. Moreover, those properties are based on the defaults of libinput itself.
So, by letting these ports just depend on xf86-input-libinput during build time instead of xlibre-xf86-input-libinput, we are not breaking anything for XLibre users because the exported properties by these drivers are based on the shared libinput library's defaults and are the same between XLibre and X.Org. (Even if we were to break anything, it would just make the default values of the GUI configuration utilities for XLibre users have different values).
The problem that we are currently facing is that the KDE Plasma 6 Desktop port not only depends on these ports in build time but also in run time, and I have found this runtime dependency to be unnecessary. I have not found anything in x11/plasma6-plasma-desktop that requires a hard dependency on these drives in runtime. I have even searched some of the Linux package repos, and they all listed these 2 drivers as build-time dependencies of plasma-desktop:
https://github.com/void-linux/void-packages/blob/master/srcpkgs/plasma-desktop/template
https://archlinux.org/packages/extra/x86_64/plasma-desktop/
By just removing the runtime dependency of x11/plasma6-plasma-desktop on these two drivers and keeping their build-time dependencies, we can solve this issue without needing to use any FLAVORs.
So just a ~2 line diff:
Diff:diff --git a/x11/plasma6-plasma-desktop/Makefile b/x11/plasma6-plasma-desktop/Makefile --- a/x11/plasma6-plasma-desktop/Makefile +++ b/x11/plasma6-plasma-desktop/Makefile @@ -19,9 +19,7 @@ LIB_DEPENDS= libcanberra.so:audio/libcanberra \ libxkbcommon.so:x11/libxkbcommon \ libxkbfile.so:x11/libxkbfile \ RUN_DEPENDS= noto-emoji>0:x11-fonts/noto-emoji \ - xdg-user-dir:devel/xdg-user-dirs \ - xf86-input-evdev>0:x11-drivers/xf86-input-evdev \ - xf86-input-libinput>0:x11-drivers/xf86-input-libinput + xdg-user-dir:devel/xdg-user-dirs USES= cmake gettext gl gnome kde:6 pkgconfig python qt:6 tar:xz xorg USE_GL= gl opengl
** The evdev input driver is also depended by plasma-desktop but it has been removed:
kcms/mouse: Remove unused xorg-evdev dependency · KDE/plasma-desktop@b4fe3e9
It's not necessary to access it directly anymore, now that we only expose settings for libinput.
diff --git a/x11/slim/Makefile b/x11/slim/Makefile
--- a/x11/slim/Makefile
+++ b/x11/slim/Makefile
@@ -18,7 +18,7 @@ RUN_DEPENDS= dbus-daemon:devel/dbus
USES= cmake compiler:c++11-lang cpe jpeg pkgconfig xorg
CPE_VENDOR= berlios
-USE_XORG= ice sm x11 xau xcb xdmcp xext xft xmu xorg-server xrandr \
+USE_XORG= ice sm x11 xau xcb xdmcp xext xft xmu xrandr \
xrender xt
USE_RC_SUBR= slim
USE_LDCONFIG= yesPage 5 has the flavor patch for xf86-video-scfb as (trimmed to show only changing lines)
+FLAVORS= xorg xlibre
+FLAVOR?= ${FLAVORS:[1]}
+
+.if ${FLAVOR} == xlibre
+PKGNAMEPREFIX= xlibre-
+USES= xlibre-cat:driver
+.else
USES= xorg-cat:driver
+.endif+FLAVORS= xorg xlibre
+FLAVOR?= ${FLAVORS:[1]}
+
+.if ${FLAVOR} == xlibre
+PKGNAMEPREFIX= xlibre-
+.endif
+USES= ${FLAVOR}-cat:driver+FLAVORS= xorg xlibre
+FLAVOR?= ${FLAVORS:[1]}
+
+PKGNAMEPREFIX= ${FLAVOR}-
+USES= ${FLAVOR}-cat:driverWait, did I miss something? I was under the impression that xlibre was now distributed as an official port and thus xlibre-ports was not necessary anymore.
pkg update followed by pkg upgrade? Will it bring in seatd? Is it now a dependency or is it optional?[2025-12-25 05:22:09] (WW) seat-libseat: libseat integration requires -keeptty which was not provided, disabling[6:37][fmc000@dabrafenib ]$ ps -auxww| grep Xorg|grep -v grep ~
root 3888 0,3 0,4 278452 116872 - S 06:24 0:04,80 /usr/local/libexec/Xorg :0 -keeptty -auth /var/dt/authdir/authfiles/A:0-ie1o3k
[6:37][fmc000@dabrafenib ]$[9:44][fmc000@dabrafenib ]$ ps -auxww| grep Xorg|grep -v grep ~
nobody 7523 1,0 0,3 275964 113284 v1 S 09:44 0:01,51 /usr/local/libexec/Xorg :0 -keeptty -auth /var/dt/authdir/authfiles/A:0-gelPnb
[9:45][fmc000@dabrafenib ]$ :0 Local local@console /usr/local/bin/X :0 -keeptty (this is only for CDE / dtlogin - other DEs may or may not need something similar);
It is still necessary because:
seatd support is enabled by default, but I have added it as a port OPTION (SEATD) and you can disable it during builds if you want to. So yes it will take in sysutils/seatd by default.
X executable (/usr/local/bin/X) is just a symlink to /usr/local/bin/Xorg)[sudo | doas | su] service seatd start
/usr/local/libexec/Xorg -seat seat0 -keepttyvideo but it can be changed in its rc script, so make sure your user is a member of that group.