Stop wondering why your package manager pulled in those weird dependencies

Technical Briefing | 11/12/2026

You run a simple install command, watch the progress bar, and suddenly your root partition has 500MB of stuff you didn’t ask for. It is usually some obscure library or a documentation package you will never touch. We blame the distro maintainers, but the real issue is how your package manager decides what a mandatory dependency looks like versus a suggestion.

The silent installation of recommended packages

Most of us forget that apt has a default behavior to pull in anything marked as Recommended. It is helpful for beginners who might need a crypto provider or a locale pack, but it is a total nightmare for minimal container images or locked-down production hosts. If you aren’t explicitly overriding this, you are bloating your disk usage with every single upgrade.

apt-get install --no-install-recommends your-package-name

• Recommends are technically optional but functionally treated as required by apt by default.
• Setting APT::Install-Recommends 0 in your config file saves significant space over time.
• Always check what would be pulled in by simulating the install before letting it run wild.

Digging into why something was dragged along

If you are already in deep and need to figure out why a specific library is currently occupying space, don’t just guess. Tools like apt-rdepends or simply inspecting the package metadata can save you hours of head-scratching. Stop accepting the bloat and force your package manager to respect your constraints.

Next time you spin up a fresh server, bake that configuration change into your base image or provisioner. It is one of those small, boring wins that pays off every time you run a full system update.