Files
computer-playbook/roles/dev-base-devel
kevinveenbirkenbachandClaude Opus 5 7bc12e55f3 fix(docs): drop the generated sections the designer merge put back
aceb5295ef moved Cosmos, Quick Setup and Credits out of the committed role
READMEs and into the documentation build's own scratch checkout, so a
committed copy can no longer go stale when the metadata moves. Merging
feature/designer (ebad39422c) took origin/main's side of those files, which
still carries them, and reinstated all 290 along with the cosmos make target
and its i8cos alias. tests/lint/ansible/roles/test_readme.py hard-fails on a
committed copy, and the reinstated Credits block credited one person with two
URLs, which tripped the credits-attribution lint as well.

Stripped with the repository's own fence-aware parser against
MANAGED_SECTIONS, not with a line filter: the Cosmos block holds a mermaid
fence a naive filter would cut through. The result is byte-identical to
aceb5295ef for every README that carries no prose change since.

The cosmos target wrote the forbidden section straight back into the
checkout, so it goes with them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-06 01:50:43 +02:00
..

Base Development Toolchain

Description

Base development toolchains provide the core build tools (compilers, linkers, make, etc.) required to compile software from source. Common examples include base-devel on Arch Linux, build-essential on Debian/Ubuntu, and @development-tools on Fedora/CentOS.

Overview

This role installs distro-specific equivalents of core build tooling so systems are ready for compiling software from source. After deploying this role, all common build dependencies are available on the system.

Features

  • Installs distro-specific base development packages:
    • Archlinux: base-devel
    • Debian/Ubuntu: build-essential
    • Fedora/CentOS: @development-tools
  • Ensures your system is ready for software compilation and development

Further Resources