Recommended Review Audience

This topic is best reviewed by Gentoo Linux Systems Administrators, Package Maintainers, and Security-focused Systems Architects. It concerns low-level configuration of the Portage package management system and the implications of deviating from standardized distribution profiles.

Abstract: Implementing a Global USE="-*" Strategy in Gentoo Linux

This documentation thread explores the advanced configuration of the Gentoo make.conf file using the USE="-*" flag to override default profile settings. The primary objective of this approach is to minimize system "bloat" by disabling all non-essential USE flags, thereby reducing the total package count—in one reported case, by 6.5% to 13%.

The process requires the user to explicitly define every required global and package-specific USE flag, as well as manually manage USE_EXPAND variables such as PYTHON_TARGETS, CPU_FLAGS_X86, and VIDEO_CARDS. While the method offers superior control and system transparency, it introduces significant maintenance overhead, including frequent dependency blockers during world updates and potential breakages in unstated dependencies. Furthermore, the discussion highlights a rift within the Gentoo community: while power users value the minimalism, administrators warn that this "self-inflicted" complexity complicates community support efforts when users fail to disclose their non-standard configurations.

Summary of Documentation: USE="-*" Implementation and Implications

• [Fri May 26, 2023 6:56 pm] Rationale for Global Masking: The author argues that default Gentoo profiles often pull in unneeded dependencies. By placing USE="-*" at the start of make.conf, a user ignores profile defaults, ensuring only explicitly enabled flags are active. This reduced the author's system from roughly 725 to 651 packages.
• [Fri May 26, 2023 6:56 pm] Prerequisites and Risks: This strategy is recommended only for veteran users. It requires proficiency in resolving Portage blockers and manual debugging. A key risk is "breakage in hard to debug ways" if a necessary but unknown flag is disabled.
• [Fri May 26, 2023 6:56 pm] Handling USE_EXPAND Variables: Users must manually define critical environment variables that the profile usually handles. This includes PYTHON_TARGETS, RUBY_TARGETS, CPU_FLAGS_X86, and VIDEO_CARDS. Failure to do so results in extensive dependency conflicts.
• [Fri May 26, 2023 7:11 pm] Diagnostic Validation: Administrators suggest running emerge --info before and after the change to audit "the damage" and identify which essential flags were lost in the transition.
• [Fri May 26, 2023 7:31 pm] Profile vs. Manual Masking: Discussion arises regarding whether a "bare-minimal" profile should be officially developed. However, proponents of USE="-*" argue it is easier to maintain personal control via make.conf than to manage a custom overlay or formal profile.
• [Fri May 26, 2023 10:02 pm] Hardware Input Nuances: A transition to USE="-*" may unset INPUT_DEVICES. In modern Gentoo, libinput is the standard; older settings like mouse and keyboard are considered outdated and may not even have available ebuilds in some configurations.
• [Sat May 27, 2023 11:30 am] Flexibility and Constraints: The author notes that USE="-*" allows for easier switching between different base system types (e.g., multilib vs. no-multilib) because it doesn't rely on the rigid inheritance of a profile, though administrators counter that such transitions are rarely "drop-in" replacements.
• [Fri Mar 15, 2024 6:17 pm] Community Support Friction: Senior administrators express frustration with the USE="-*" paradigm. They note that users often seek help for "bizarre issues" without disclosing their global mask, wasting volunteer time on problems caused by the user's refusal to use "sane defaults."
• [Sat Mar 16, 2024 3:12 am] The "Anti-Bloat" Philosophy: Participants categorize this approach as part of the "fundamentalist anti-bloat" movement. While valuable for security and maintenance, it is criticized for a lack of warnings when users advise others to adopt the practice.
• [Sat Mar 23, 2024 7:53 pm] Specific Package Exceptions: Real-world testing shows specific packages, such as dev-lisp/clisp, require manual intervention (e.g., USE="-* unicode") just to successfully compile under this regime.