vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: D-Bus, boot, wayland plans → v3.0 parent references

Browse Source 
- DBUS-INTEGRATION-PLAN.md: parent plan v2.0→v3.0, redbear-kde→redbear-full
- BOOT-PROCESS-IMPROVEMENT-PLAN.md: v2.0→v3.0, redbear-kde→redbear-full
- WAYLAND-IMPLEMENTATION-PLAN.md: redbear-wayland/kde marked historical

All active doc parent plan references now point to CONSOLE-TO-KDE-DESKTOP-PLAN.md v3.0.
This commit is contained in:
Vasilito
2026-04-29 14:31:53 +01:00
parent 3f732fa4be
commit ac1da6065b
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/docs/DBUS-INTEGRATION-PLAN.md
+2 -2
View File
@@ -3,7 +3,7 @@
**Version:** 1.0 — 2026-04-17
**Status:** Active plan
**Scope:** Full D-Bus infrastructure for KDE Plasma 6 on Wayland, tightly integrated with Redox scheme IPC
**Parent plan:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v2.0)
**Parent plan:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v3.0)
---
@@ -13,7 +13,7 @@ D-Bus is **mandatory infrastructure** for KDE Plasma 6 — not optional, not def
services, KWin, plasmashell, and virtually every KF6 framework communicate over D-Bus at runtime.
Red Bear OS already has D-Bus 1.16.2 building with a 24-line redox.patch, the system bus wired
in `redbear-full` and `redbear-kde` profiles, and QtDBus enabled in qtbase. This is a solid
in `redbear-full` profile (historical `redbear-kde` name retired), and QtDBus enabled in qtbase. This is a solid
foundation, but it is only the transport layer. What's missing is the **service layer** — the
D-Bus services that KDE actually expects to talk to.