From 67839a09144dacb75d7c37a1f24c73e691af35d8 Mon Sep 17 00:00:00 2001 From: Vasilito Date: Wed, 15 Apr 2026 12:57:07 +0100 Subject: [PATCH] Annotate historical driver and KDE docs Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus --- docs/04-LINUX-DRIVER-COMPAT.md | 5 +++++ docs/05-KDE-PLASMA-ON-REDOX.md | 18 ++++++++++++++++++ 2 files changed, 23 insertions(+) diff --git a/docs/04-LINUX-DRIVER-COMPAT.md b/docs/04-LINUX-DRIVER-COMPAT.md index 9bfc188a..ed916061 100644 --- a/docs/04-LINUX-DRIVER-COMPAT.md +++ b/docs/04-LINUX-DRIVER-COMPAT.md @@ -320,6 +320,11 @@ tar cf intel-driver.tar linux/drivers/gpu/drm/i915/ \ ### Step 2: Create recipe +> **Historical recipe note:** the `recipes/wip/drivers/...` example below is part of the original +> upstream-oriented porting path. Under the Red Bear overlay policy, upstream WIP driver recipes are +> still useful inputs, but the fixed/shipping version may need to live under `local/recipes/` until +> upstream promotes them to first-class status. + ```toml # recipes/wip/drivers/i915/recipe.toml [source] diff --git a/docs/05-KDE-PLASMA-ON-REDOX.md b/docs/05-KDE-PLASMA-ON-REDOX.md index 065135e3..1eb37883 100644 --- a/docs/05-KDE-PLASMA-ON-REDOX.md +++ b/docs/05-KDE-PLASMA-ON-REDOX.md @@ -5,6 +5,11 @@ > exist under `local/recipes/kde/`, and the current gap is no longer "start KDE from scratch". > The real frontier is distinguishing true builds from shimmed/stubbed packages and then closing > the KWin / Plasma runtime path. +> +> For the current build/runtime truth summary of the desktop stack, use +> `local/docs/DESKTOP-STACK-CURRENT-STATUS.md` together with +> `local/docs/QT6-PORT-STATUS.md`. This file should now be read primarily as implementation history +> plus deeper KDE-specific rationale and porting notes. ## Current State Snapshot @@ -77,6 +82,10 @@ Blocked on: KF6 completion, Mesa EGL/GBM, libdrm amdgpu+intel #### Step 1: Port `qtbase` (6-8 weeks) +> **Historical recipe note:** the `recipes/wip/qt/...` path below is retained as design history. +> For current Red Bear ownership and shipping decisions, use the WIP ownership policy and current +> local overlay docs rather than assuming upstream WIP is the preferred final source. + **Create recipe**: `recipes/wip/qt/qtbase/recipe.toml` ```toml @@ -236,6 +245,11 @@ These have minimal dependencies — just Qt and CMake. | `kguiaddons` | GUI utilities | None — pure Qt | **Recipe pattern** (same for all Tier 1): + +> **Historical recipe pattern note:** the `recipes/wip/kde/...` examples below show the original +> upstream-oriented porting pattern. Current Red Bear-owned KDE shipping work should prefer +> `local/recipes/kde/` while upstream KDE recipes remain WIP. + ```toml # recipes/wip/kde/kcoreaddons/recipe.toml [source] @@ -476,6 +490,10 @@ plasmashell & ## KDE Applications (Build on 19 WIP Recipes) +> **WIP ownership note:** the application list below is useful as an upstream-WIP inventory, but it +> is not by itself a statement that Red Bear should ship directly from upstream `recipes/wip/kde/`. +> Apply the WIP migration ledger when deciding local-versus-upstream ownership. + These are already partially ported in `recipes/wip/kde/`: | App | Status | Notes |