Package Managers

nixpkgs24.2k★

The largest collection of software packages in any package manager, over 100,000 packages, more than Debian, AUR, or Homebrew. If you've ever struggled with "works on my machine" problems, dependency conflicts, or reproducible builds, Nix (the package manager) and nixpkgs (this package collection) solve that by making every package build in isolation with its exact dependencies. Every package is built in a sandbox with only its declared dependencies available. No global state, no dependency conflicts, no breaking one thing by updating another. You can have Python 3.8 and 3.12 installed simultaneously without them interfering. Roll back any change instantly. Define your entire system configuration as code. Completely free under MIT. Community-maintained with major backing from Determinate Systems, Flox, and other companies building on the Nix ecosystem. Homebrew is the pragmatic alternative, less powerful but dramatically easier to use. Guix is the GNU alternative with a Scheme-based approach. If you just need reproducible dev environments, devenv or devbox abstract away Nix's complexity while using nixpkgs underneath. The catch: the learning curve is brutal. Nix has its own functional programming language for package definitions. The documentation has historically been fragmented and confusing (it's improving). Error messages are often cryptic. You'll spend hours learning before you save hours building. The community is passionate but has had governance growing pains.

Nix16.5k★

Nix is a package manager that makes builds reproducible, solving the 'works on my machine' problem caused by different system packages and library versions. Every package is built in isolation with its exact dependencies, so "works on my machine" becomes "works on every machine." It can also manage your entire operating system (NixOS) or just your development environments. Fully free under LGPL 2.1. Over 100,000 packages in Nixpkgs (one of the largest package repositories in existence). Use it to create development shells where every team member gets identical tool versions, build Docker images with precise dependencies, or manage server configurations declaratively. The catch: the learning curve is brutal. The Nix language is functional and unlike anything most developers have seen. Documentation is notoriously scattered across the official manual, wiki, and community blogs. You'll spend days figuring out what takes 5 minutes in other package managers. The payoff is real, but so is the investment. If reproducibility isn't a pain point for you, Nix is a solution looking for a problem.

NUR1.8k★

NUR is the community package overlay for Nix. If a package isn't in nixpkgs (the main Nix repository), NUR is where the community publishes it. No review process, no merge queue, just add your repo and it's available to every Nix user. Completely free, MIT licensed. Setup is one line in your Nix configuration. Point your flake or channel at NUR, and you get access to hundreds of user-contributed packages. There's nothing to host or maintain on your end. The NUR infrastructure runs as a GitHub-based build system that aggregates community repos. This is exclusively for Nix users. If you're already managing systems or dev environments with Nix and keep hitting missing packages in nixpkgs, NUR fills the gap without forking or maintaining your own overlay. The catch: no quality guarantees. Packages in NUR aren't reviewed like nixpkgs contributions. You're trusting individual maintainers. And if you're not already using Nix, NUR solves a problem you don't have.

bioconda-recipes1.8k★

Bioconda is a conda channel with 10,000+ pre-built packages for biological research software. Instead of compiling BLAST, SAMtools, or BWA from source and fighting with library versions, you type `conda install samtools` and it works. MIT license. This repo contains the recipes (build instructions) for every package in the Bioconda channel. It's community-maintained by hundreds of bioinformaticians who are tired of broken builds. Everything is free. Bioconda is a community project. No paid tier, no commercial version. Conda itself is free (use Miniforge to avoid Anaconda's commercial licensing complications). The catch: this is a niche tool for a niche field. If you're not doing bioinformatics, you don't need this. If you are, it's essentially mandatory. The alternative is spending days compiling tools from source and resolving C library conflicts. The conda solver can be slow for complex environments (use mamba instead of conda for faster solves). And some packages lag behind upstream releases by days or weeks.

macports-ports1.8k★

MacPorts is one of the original package managers for that. It compiles software from source (or uses prebuilt binaries when available) and installs it in /opt/local, keeping it separate from Apple's system files, on the ports tree repo (the actual packages), but MacPorts as a project has been running since 2002. Over 30,000 ports available. Tcl-based port definitions. BSD-style. Fully free. Community-maintained, no paid tier, no commercial entity behind it. The honest take: most Mac developers use Homebrew instead, and for good reason. Homebrew is easier to use, installs faster (prebuilt bottles for almost everything), and has a much larger community. MacPorts compiles from source more often, which means slower installs but more control over build options and variants. MacPorts still makes sense if you need precise control over compile-time options, if you work in scientific computing where specific library versions matter, or if you've been using it for 20 years and your workflow depends on it. The catch: the community is smaller, packages update slower than Homebrew, and most online tutorials assume Homebrew. If you're starting fresh on macOS, Homebrew is the pragmatic choice unless you have a specific reason for MacPorts.