Apt-bundle: brew bundle for apt

Apt-bundle promises one-file setup for Linux—fans cheer, skeptics roll their eyes

TLDR: Apt-bundle brings a simple file to set up Linux apps in one go, aiming for Homebrew-style ease. The crowd applauds convenience but argues over missing automatic removals and needing sudo, while jokers escalate it with meta-tools—showing both hype and hesitation around how Linux should be managed.

Linux gets its own “Brewfile” moment: apt-bundle claims you can list everything your computer needs in a single “Aptfile” and set it up with one command. Think easy onboarding, repeatable installs, version pinning, and adding outside sources without fiddly steps. The crowd split fast. Excited users love the “one-file to rule them all” vibe, while purists grumble this is just fancy packaging for scripts. lifetimerubyist delivered the classic eye-roll: you’re just avoiding bash. Meanwhile, pamcake turned it into a meme, announcing a meta-tool called “apt-bundle-bunch” with an “Aptbundlefile” and even a cheeky curl-to-shell install with Claude—yes, it’s getting absurd, and that’s the joke.

Then came the hardliners. pzmarzly pointed out a big gap: apt-bundle installs new things but doesn’t remove stuff you took out of your list—one of Homebrew’s best tricks. That’s drama in package-land. curt15 added a security-flavored zinger: unlike macOS’s Homebrew, apt still wants you to run things with sudo (system-level powers), while Homebrew actually blocks you if you try (link). On the other side, jbverschoor quietly shipped it into their dev setup file and moved on—proof some folks just want it to work. And topping it off, someone asked if it was “vibe coded,” which is internet-speak for “did you build this on vibes alone?” The mood: hopeful, chaotic, and extremely online.

Key Points

  • Apt-bundle is a declarative wrapper for apt, inspired by brew bundle, to manage packages and repositories on Debian-based systems.
  • It uses an Aptfile to define packages, PPAs, custom repositories, GPG keys, and supports version pinning with idempotent operations.
  • Installation options include a curl-based script, manual .deb installation from GitHub releases, and building from source with make.
  • CLI usage includes install, check, dump, file selection, and an option to skip apt update; binary installs to /usr/local/bin.
  • Examples and use cases cover developer onboarding, Dockerfile integration with multiple approaches, and system sync across machines.

Hottest takes

"man the things people come up with to avoid writing bash scripts" — lifetimerubyist
"it only installs new packages, but doesn't uninstall removed ones" — pzmarzly
"doesn't require root and even errors out if run as root" — curt15
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.