Gentoo USE Flags for Headless Servers

Problem: Unnecessary graphical libraries on a headless server

When installing Gentoo on a machine that will never run a desktop, many packages still pull in X11, GTK, or Qt libraries because their default USE flags enable those features. This inflates the installed footprint, lengthens compile times, and adds code that is never used.

Thesis: USE flags let you make a deliberate, compile‑time decision to drop those optional features, giving you an auditable way to reduce the system’s attack surface and rebuild set.

How USE flags work in Portage

Portage reads USE flags from three layers: the global /etc/portage/make.conf, per‑package overrides in /etc/portage/package.use, and the active profile (e.g., default/linux/amd64/17.0/desktop). A flag such as X maps to the upstream --with-x configure switch; setting -X disables it.

Worked example: disabling graphical support globally

1. Check current flags: emerge --info | grep USE (run as root or with sudo).
2. Add a global override: edit /etc/portage/make.conf and append USE="... -X -wayland -gtk -qt5" (replace ... with existing flags).
3. Preview the impact before rebuilding: emerge --ask --verbose --update --deep --newuse @world. The output shows which packages would change and why, highlighted in color.
4. If the preview looks acceptable, proceed: emerge --update --deep --newuse @world. This will rebuild only the packages whose dependencies actually change.
5. Verify: after the rebuild, run equery hasuse X to see which installed packages still have the flag enabled (should be none unless a package hard‑depends on X).

Trade‑offs and limits

• Source builds take time; on modest hardware a full @world update can take hours.
• Changing a flag can trigger a large rebuild cascade because many packages depend on the affected libraries.
• If a package has a hard dependency on X (e.g., media-gfx/imagemagick with X support), disabling -X will cause emerge to report a conflict; you must either keep the flag for that package via /etc/portage/package.use or accept that the package cannot be installed.
• The official Gentoo binhost only provides packages built for common USE flag combinations; heavily customized flags will fall back to source builds, reducing the benefit of binary packages.

Actionable closing

Start small: test a flag change on a single package using /etc/portage/package.use, rebuild it, and confirm the runtime behavior before applying the change globally. Use equery uses to see which flags a package supports, and emerge --ask --verbose --update --deep --newuse @world to preview impacts. This iterative approach lets you reap the footprint and security benefits of USE flags without risking an unsolvable dependency graph.