Gentoo_Style_Arch

Gentoo_Style_Arch is a curated Arch Linux package set for rebuilding a large, dependency-coupled desktop and toolchain stack from PKGBUILD recipes. It contains the recipes and the scheduler; it does not vendor upstream source trees, package archives, build outputs, or downloaded signatures.

The project is intentionally Arch-specific. Every PKGBUILD is executable shell code and may fetch and build software with the privileges and network access available to makepkg. Read the recipe and the security guidance before building or installing anything.

The set is maintained for AMD laptops: AMD CPUs with amdgpu/radeon graphics. Hardware-support trims follow from that target — a recipe may drop Intel- and NVIDIA-only firmware, drivers and code paths — while the recipes themselves are written to build on any Arch x86_64 host, deriving ISA settings from the environment rather than pinning one. Packages built from this tree are tuned to the building machine (see docs/portability.md) and are not redistributable binaries. Trimming has been exercised on one AMD model, so treat "AMD laptop, any" as the intent and a second model as useful verification.

What is included

The current set has 146 recipe directories and 149 group memberships (counts from the groups fields in config/topology.conf, cross-checked with fish build-all.fish --list -g <group>). The counts differ because hip-runtime, hsa-rocr and openssl are stable,core records counted in both groups; core is a logical build group whose 40 members span the physical layout: 35 live under packages/core/, autofdo-git and libclc-git come from packages/git/, and the three stable,core members from packages/stable/:

Group	Members	Purpose
git	42	Top-level development and rolling packages
stable	44	Stock-name packages synchronized with Arch repositories (grew 27 → 44 with the 2026-09-28 leaf-utility batch)
core	40	Heavy, ABI-coupled, source-heavy, and ROCm packages
misc	1	Optional CachyOS kernel recipe
app	22	Optional applications; a TTY build/-n run prompts to multi-select (all unchecked + Enter = build all; records sharing an app-cluster tag toggle as one row); leaf builds — app packages typically have no consumers to expand

Package records — the ID-to-path binding, group membership, the local build-order graph, and coupled-batch tags — are declarative, one record per package in config/topology.conf (id|path|groups|edges[|tags]); do not infer build order from directory names.

Fresh checkout

On an Arch-based system, install the normal packaging tools first:

sudo pacman -S --needed base-devel fish git ripgrep

Then inspect the project before building:

fish build-all.fish --help
fish build-all.fish --list
fish build-all.fish --audit
fish build-all.fish --dry-run --group git

Validate a change with the fixture battery (tests/) — it is fast and non-mutating — and with makepkg's own checks. tools/ holds host-side diagnostics that are deliberately too heavy for that battery:

bash tests/run-all.sh                  # every fixture (parallel by default)
bash tests/run-all.sh recipe           # substring filter
bash tests/run-all.sh --serial         # one at a time
tools/go-modcache-check.sh             # is the Go module cache intact?

Build a selected group or package. Selection is mandatory; a bare invocation never starts an unattended full rebuild. A selection expands to the named packages plus their transitive consumers — the packages that must rebuild after them — in build order; prerequisites are assumed installed and current. --no-deps rebuilds exactly what is named:

fish build-all.fish --group git
fish build-all.fish --group core
fish build-all.fish glib2-git               # glib2-git and its consumers
fish build-all.fish --no-deps glib2-git     # glib2-git alone

Use --install only when the immediately installed package state is desired. A package whose exact version is already installed (with an install date not older than its archive) skips its transaction; --forceinstall implies --install and always installs. Unprivileged runs use sudo for each transaction; long runs are generally more reliable when the supervisor is started as:

sudo fish build-all.fish --group core

The builder still runs makepkg as the invoking user in root-supervisor mode. See docs/build-guide.md before using installation or cleanup modes.

Adaptive parallelism

The default --intensity xhigh profile derives concurrency from available CPU threads and MemAvailable. It budgets normal-lane jobs globally, rather than granting every lane an independent memory allowance. Heavy core recipes run alone with a separate memory-aware job limit.

Choose a named effort profile when automatic scheduling should be less or more aggressive:

Profile	Intent
low	One conservative lane; maximize memory headroom
medium	Balanced baseline for long-running hosts
high	More independent lanes and lower per-job memory budget
xhigh	Default; aggressive utilization with bounded automatic lanes
max	Highest automatic utilization; use only when OOM risk is acceptable

Override the plan explicitly when needed:

fish build-all.fish --group git --intensity medium
fish build-all.fish --group git --lanes 1 --jobs 2
GSA_INTENSITY=low fish build-all.fish --group git

GSA_CPU_THREADS and GSA_MEMORY_GIB are also available for constrained containers and deterministic scheduler fixtures. Normally they should be left unset so the host's /proc and nproc values are used. Explicit --lanes and --jobs values take precedence over the profile.

Runtime logs, lane results, and locks are written under .state/ by default and are ignored by Git. makepkg source trees and package archives remain beside their recipe unless your makepkg configuration directs them elsewhere; those classes are also ignored. Set GSA_STATE_DIR to keep builder state outside the checkout.

Source policy

Remote Git repositories, release archives, PGP key caches, and build trees are deliberately absent. A clean checkout fetches them through the source=() entries in each recipe. Local patches, hooks, install scripts, desktop files, configuration inputs, licenses, and .SRCINFO files are retained because they are part of the packaging work.

--link-sources can deduplicate compatible VCS mirrors after sources have been fetched. Shared mirrors are runtime state and must not be committed.

Licensing

LICENSE applies only to the original scheduler and project documentation. Recipes contain upstream/AUR material with their own copyright, license, maintainer, checksum, and source terms. Preserve the package-local metadata when redistributing or modifying a recipe.

See:

• docs/build-guide.md for operations and cleanup;
• docs/portability.md for CPU, RAM, ISA, and profile controls;
• docs/maintainer-guide.md for recipe and dependency maintenance;
• docs/MEMORY.md and docs/NOTE.md for the retained operational history;
• SECURITY.md before running a new or changed recipe.