The blanket reading from commit 5396e6c3c would have forced every direct
edit to mesa, wayland, qt, KF6, KWin, SDDM, llvm, libdrm, redox-drm,
libepoxy, and similar multi-million-line external projects to live
inside recipes/<pkg>/source/, where a 'make clean' or upstream sync
would silently clobber our work. That is not a full fork, that is a
liability.
Replace the single hard prohibition with a two-rule model:
Rule 1 — In-tree Red Bear components (kernel, relibc, base, installer,
bootloader) and small Red Bear-initiated packages: NO overlay, NO
local fork of mainline. Direct edits in recipes/<pkg>/source/ and
recipes/<pkg>/recipe.toml. No symlinks, no patch files.
Rule 2 — Big external projects (mesa, wayland, qt, KF6, KWin, SDDM,
llvm, libdrm, redox-drm, libepoxy, etc.): Red Bear fork at
local/sources/<component>/ is mandatory. The mainline recipe points
at the fork via 'git = ...' or a 'Local' source type. We own the
source, the recipe just builds it.
Both AGENTS.md (top-level) and local/AGENTS.md updated. Cross-references
to the section name in the anti-pattern tables at the bottom of the
policy remain valid.
vasilito
2b72f61e41