You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to install KDE 6 + Wayland on FreeBSD 14.1. I've asked some help on the ML of FreeBSD and a developer told me that I can install KDE 6 + Wayland and sent a screenshot that showed that it can be done. There is an interesting part that involves cheribsd. He said :
==> sysrc seatd_enable="YES"
Plasma cannot use seatd without : 02e468a397ad
So,I need to make you some questions :
Should I make the installation of plasma5-kwin from ports even if I want to install KDE Plasma 6 ?
CHERI BSD is merely a port of FreeBSD for a special processor. I'm not sure that it will help with KDE co-installability issues. I would like to know if the patches proposed above have the purpose to fix the problem.
I suspect that KDE 5 stuff cannot be installed side-by-side on the same host as KDE 6. The FreeBSD-KDE team knows that much. Reason being - 5 and 6 have components with the same names that are installed into the same places. x11-wm/plasma6-kwin, and x11-wm/plasma5-kwin cannot be installed on the same host. Do you agree ?
The text was updated successfully, but these errors were encountered:
CheriBSD tries to be as close as possible to FreeBSD and does not change the way FreeBSD ports work in general. There might be some differences (workarounds) between FreeBSD ports and CheriBSD ports due to the lack of patches that would be needed to make certain functionalities in FreeBSD ports work on CheriBSD and CHERI. We don't maintain upstream FreeBSD ports that we use in CheriBSD ports and hence I'm afraid you might not be able to get a satisfying answer to your question here.
Should I make the installation of plasma5-kwin from ports even if I want to install KDE Plasma 6 ?
We don't have KDE Plasma 6 (nor Qt6 required by it) available for CheriBSD. There has been some work on KDE6/Qt6 from @arichardson but I don't know what is the state of that work.
CHERI BSD is merely a port of FreeBSD for a special processor. I'm not sure that it will help with KDE co-installability issues. I would like to know if the patches proposed above have the purpose to fix the problem.
If you mean 02e468a397ad by "patches", that commit was added not to solve issues between KDE 5 and KDE 6 but to work around the lack of ConsoleKit2 on CheriBSD, as explained in that commit message.
I suspect that KDE 5 stuff cannot be installed side-by-side on the same host as KDE 6. The FreeBSD-KDE team knows that much. Reason being - 5 and 6 have components with the same names that are installed into the same places. x11-wm/plasma6-kwin, and x11-wm/plasma5-kwin cannot be installed on the same host. Do you agree ?
If I understand correctly, you try to use CheriBSD ports on FreeBSD. That is not supported. If you want to use 02e468a397ad on FreeBSD, you will have to cherry-pick that change into a FreeBSD ports branch and try to make your environment work from there.
Hello.
I'm trying to install KDE 6 + Wayland on FreeBSD 14.1. I've asked some help on the ML of FreeBSD and a developer told me that I can install KDE 6 + Wayland and sent a screenshot that showed that it can be done. There is an interesting part that involves cheribsd. He said :
So,I need to make you some questions :
Should I make the installation of plasma5-kwin from ports even if I want to install KDE Plasma 6 ?
CHERI BSD is merely a port of FreeBSD for a special processor. I'm not sure that it will help with KDE co-installability issues. I would like to know if the patches proposed above have the purpose to fix the problem.
I suspect that KDE 5 stuff cannot be installed side-by-side on the same host as KDE 6. The FreeBSD-KDE team knows that much. Reason being - 5 and 6 have components with the same names that are installed into the same places. x11-wm/plasma6-kwin, and x11-wm/plasma5-kwin cannot be installed on the same host. Do you agree ?
The text was updated successfully, but these errors were encountered: