vasilito
4a37ae1a57
Per AGENTS.md § 'Local Fork Recipe Directories Must Not Carry Patch
Files', the symlinks under recipes/core/{base,kernel,relibc,
bootloader,installer}/ pointing at the canonical local/patches/<comp>/
patches were violations. The recipes use path = '...' source so the
cookbook would never apply these patches; the symlinks were a
navigation aid only.
This commit moves all 137 valid symlinks (and the redox.patch
counterparts) to local/docs/legacy-recipe-patches/<comp>/ with a
README explaining the rationale and pointing readers at the canonical
patch location.
The patches themselves (local/patches/<comp>/*.patch) are NOT
modified — they remain git-tracked at their canonical location.
Per AGENTS.md 'NEVER DELETE' policy the patches stay in their
canonical home; only the navigation aid symlinks are relocated.
Breakdown:
base (61) - legacy-recipe-patches/base/
kernel (26) - legacy-recipe-patches/kernel/
relibc (46) - legacy-recipe-patches/relibc/
bootloader (3) - legacy-recipe-patches/bootloader/
installer (1) - legacy-recipe-patches/installer/
After this commit, recipes/core/<comp>/.patch references all show
zero matches per AGENTS.md rule.
1.4 KiB
Legacy Recipe Patch References
These .patch symlinks previously lived under recipes/core/<comp>/
as visible-by-navigating references to the patches that modified each
fork. After the 2026-07 refactor (fork patches fully absorbed into
fork commits), the symlinks violated AGENTS.md § "Local Fork Recipe
Directories Must Not Carry Patch Files" and were moved here.
What's in here
For each affected component, a directory of symlinks points at the
real patch files in local/patches/<comp>/. The patches are git-
tracked both here and in their canonical local/patches/<comp>/
location — these legacy symlinks are a navigation aid only.
Why we keep them
Per AGENTS.md "absolutely NEVER delete" rule, these patches represent
durable Red Bear work that must never be removed. Moving the symlinks
out of recipes/core/<comp>/ (where the cookbook would never apply
them because recipes use path = "..." source for the local fork)
cleans up the build-system surface while preserving the historical
record.
Affected components
- base (61 legacy patches)
- kernel (26 legacy patches)
- relibc (46 legacy patches)
- bootloader (3 legacy patches)
- installer (1 legacy patch)
Total: 137 legacy patch references.
If a fork is ever re-fetched from upstream and a Phase 0+1 patch
recovery commit is lost, the patches under local/patches/<comp>/
remain untouched and can be re-applied via local/scripts/apply-patches.sh.