Process 1: Analyze and Adopt

Domain: Linux Systems Administration / Software Engineering (Gentoo Linux Infrastructure) Persona: Senior Gentoo Systems Architect and Release Engineer

Process 2: Reviewer Identification

The ideal group to review this topic consists of Gentoo Release Engineers, Toolchain Maintainers, and Power Users interested in system minimization. These experts focus on the intersection of package management (Portage), dependency resolution, and system security.

Process 3: Summary

Abstract: This technical discussion examines the implementation of USE="-*" within the Gentoo Linux environment. By setting USE="-*" in make.conf, a user effectively nullifies all default USE flags provided by the system profile, necessitating the explicit definition of every desired functional flag. The documentation outlines the methodology for transitioning to this state, emphasizing the reduction of system "bloat"—reporting package count reductions of 6% to 13%. Key technical requirements include the manual configuration of USE_EXPAND variables (e.g., PYTHON_TARGETS, CPU_FLAGS_X86) and the resolution of complex portage blockers. While proponents argue for increased security through reduced attack surfaces and absolute dependency control, senior administrators highlight significant pitfalls. These include increased maintenance overhead, potential breakages in software lacking explicit dependencies (e.g., imlib2, clisp), and the ethical burden on community volunteers when troubleshooting "self-inflicted" issues on non-standard, "minimalist" configurations.

Technical Documentation and Community Discussion: Implementing USE="-*"

• May 26, 2023, 6:56 pm | Motivation and Logic: The primary driver for USE="-*" is the bypass of "sane defaults" in profiles that pull in unneeded dependencies. Setting this flag ensures that only explicitly enabled features are compiled, preventing new profile-level flags from automatically adding unwanted packages during world updates.
• May 26, 2023, 6:56 pm | Implementation Strategy: To transition, the user must add -* as the first entry in the USE string of make.conf. This forces a shift from global make.conf management to granular package.use management.
• May 26, 2023, 6:56 pm | Mandatory Variables: Setting USE="-*" requires manual definition of USE_EXPAND variables. Critical variables include PYTHON_TARGETS, CPU_FLAGS_X86, VIDEO_CARDS, and LUA_SINGLE_TARGET. Failure to set these results in significant dependency blockers during @world updates.
• May 26, 2023, 7:11 pm | Input Device Caveats: Administrators note that variables like INPUT_DEVICES may default to empty strings under this configuration. For modern X11 setups, explicitly setting INPUT_DEVICES="libinput" is recommended, though users with static /dev setups (avoiding udev) may require legacy mouse and keyboard drivers.
• May 27, 2023, 11:30 am | Profile vs. Manual Flagging: Discussion arises regarding the creation of a "bare-minimal" profile. The consensus suggests that USE="-*" is more flexible for individual power users as it allows for easier switching between glibc/musl or multilib architectures without the overhead of maintaining a custom profile.
• March 15, 2024, 6:17 pm | Support Ethics and Disclosure: A major point of contention is the "tinderbox" nature of these systems. Administrators demand that users clearly disclose the use of USE="-*" when seeking help, as it creates non-standard failure modes that consume volunteer time unnecessarily.
• March 26, 2024, 10:51 pm | Tooling Behavior: Functional tests show that emerge --info may filter out the -* string from reported output, showing only the resulting enabled flags. This can obscure the underlying configuration from developers during bug reporting.
• April 9, 2024, 5:28 am | Advanced Minimization: Users suggest further refining the system by nullifying PYTHON_TARGETS and PYTHON_SINGLE_TARGET in make.conf, then enabling Python support only for the specific ebuilds that strictly require it.
• July 14, 2024, 2:43 pm | Benchmarking a Modern Install: A case study of a KDE Plasma 5 installation with USE="-*" resulted in 376 packages—roughly half the size of a standard Plasma profile installation. This confirms the efficacy of the method for aggressive de-bloating in complex desktop environments.
• August 15, 2024, 11:57 am | Security and Hardening: While minimization increases security by removing code, certain flags like xattr are identified as necessary for hardened systems (e.g., for file capabilities). Users must balance the "anti-bloat" philosophy with the need for security-critical flags like default-stack-clash-protection and default-znow which are often hard-enabled in profiles.