Replaces the raw package modules at 76 call sites with package_install, moves each role's distribution mapping into its own meta/packages.yml, and turns the inventory PACKAGES variable from source-keyed literal names into a list of declared package ids. The lint that forbids the raw modules is enabled here, because the migration burns it down from 76 offenders to zero. Removes sys-aur, sys-aur-install and sys-package. The AUR build user, the passwordless pacman rule and the inventory-driven install are part of the plan the action plugin executes, so the roles no longer carry them. Declaring the mappings surfaced breakage the raw modules had hidden: on Debian the `which` binary comes from debianutils, jrnl is in no Debian or Ubuntu suite, chromium-browser is absent from Debian stable, JDK 11 is unobtainable on RedHat, wireguard had no RedHat branch at all, qbittorrent was built from the AUR although Arch ships it in extra, and desk-docker installed a Docker variant that conflicts with the one sys-svc-container installs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
GCC
Description
This Ansible role installs the GNU Compiler Collection (GCC) on Arch Linux systems. GCC is a standard compiler suite supporting C, C++, and other programming languages. It is a core component for compiling and building software from source.
Learn more about GCC on Wikipedia, the official GCC homepage, and the Arch Linux Wiki.
Overview
Tailored for Arch Linux, this role installs GCC and optionally sets up additional development utilities. It ensures the package is installed via the system package manager and ready to compile code in a variety of programming languages.
Cosmos
The diagram places GCC in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph role [dev-gcc 💻]
svc_gcc["gcc"]
end
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments). Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Purpose
The purpose of this role is to automate the provisioning of a development-ready environment by ensuring the GCC toolchain is properly installed and available.
Features
- Installs GCC: Uses
pacmanto install thegccpackage. - Minimal Setup: No unnecessary dependencies are installed.
- Reusable Role: Can be used as a foundational component for software development, CI/CD pipelines, and build environments.
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).