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

Annotate historical driver and KDE docs

Browse Source 
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This commit is contained in:
Vasilito
2026-04-15 12:57:07 +01:00
parent e6499a516b
commit 67839a0914
2 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/04-LINUX-DRIVER-COMPAT.md
+5
View File
@@ -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]
docs/05-KDE-PLASMA-ON-REDOX.md
+18
View File
@@ -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 |