liveBook · Manning

Package manager

As explained in Developer Experience on Kubernetes

A package manager is a software tool that installs, resolves, builds, and manages distributable software packages and their dependencies.

A package manager installs and maintains the tools a development environment depends on. Traditional managers are convenient, but their operating-system and CPU-architecture assumptions can make team setup difficult: Homebrew, apt, dnf, and Scoop each cover different environments, while globally installed packages can force unrelated projects to share one version. section 2.2.6

Package-manager choices shape the inner-loop workflow in several ways:

  • Portability: choose tools that work across the operating systems and AMD64 or ARM64 architectures used by the team, especially inside Linux-based Devcontainers. section 2.2.6
  • Version isolation: use SDKMAN! or mise-en-place when different projects need different versions of the same package instead of sharing one global installation. section 2.2.6
  • Reproducibility: use Nix to declare packages that are built in isolated, hermetic environments and support multiple systems and architectures. section 2.2.6 section 2.5

A project-local Flox environment

A Flox manifest can declare Go and HTTPie under an install section and list supported systems such as aarch64-darwin, aarch64-linux, x86_64-darwin, and x86_64-linux. Activating the environment produces a hermetic workspace whose tools are available to the project rather than relying on a matching global installation. section 2.2.6

Listing 2.3 Example of Flox configuration file.
version = 1 #A
 
[install] #B
go.pkg-path = "go"
httpie.pkg-path = "httpie"
 
[options]
systems = [ #C
  "aarch64-darwin",
  "aarch64-linux",
  "x86_64-darwin",
  "x86_64-linux",
]

Inspect the compact Flox configuration to see how package declarations and supported system targets make a development environment portable and declarative. section 2.2.6

How Developer Experience on Kubernetes covers it

How deep it goes
Explains global installation limits, project-specific versions, and reproducible environments, without descending into package-manager implementation internals.
Examples
Uses Homebrew, apt, dnf, Scoop, SDKMAN!, mise-en-place, Nix, and a Flox manifest containing Go and HTTPie.
What it assumes
Assumes familiarity with installing developer tools and introduces the portability, versioning, isolation, and reproducibility problems behind environment choices.
What you can do after
Operate/configure project environments with reproducible, isolated, portable tool installations and controlled package versions.
How it connects
Connects package managers with development environments, Devcontainers, Nix, Flox, SDKMAN!, mise-en-place, and architecture portability.

Also explained in

Compare how 6 books explain package manager →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.