ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A decision guide for Emacs package management: compare package.el+use-package, straight.el, and Elpaca on reproducibility, speed, and patching, with a minimal working config and validation steps.
Goal I want an Emacs configuration I can reproduce on a fresh machine with minimal manual steps, and I am deciding between the built-in package.el and straight.el as the package manager. Assume Emacs 29 or later. The trade-off as I understand it package.el ships with Emacs and installs into ~/.emacs.d/elpa, but reproducibility seems to depend on me manually
Deterministic Configuration on Isolated Workstations Maintaining a reproducible Emacs environment on an air-gapped workstation requires a strategy for package management that ensures a cold start results in the exact same byte-code and feature set across different machine images. Using the built-in package.el with local ELPA mirrors provides a minimal bootst