3 ms·
If you want to build and install custom packages which in turn depend on libraries which are newer than system packages, this sounds like a perfect use case for
by jnxx 6y ago
If you want to build and install custom packages which in turn depend on libraries which are newer than system packages, this sounds like a perfect use case for GNU Guix as a package manager (e.g. on top of Debian or Arch):
http://guix.gnu.org/cookbook/en/guix-cookbook.html#Advanced-package-management http://guix.gnu.org/cookbook/en/guix-cookbook.html#Advanced-...
With this, you can create isolated environments in which you can work on specific software, and use and go back to arbitrary versions, without cluttering the base system with local installations. One of the best features is that defining an additional package oneself is merely an extension of the package definitions available with Guix:
https://guix.gnu.org/cookbook/en/html_node/Packaging-Tutorial.html https://guix.gnu.org/cookbook/en/html_node/Packaging-Tutoria...
And, of course, it works well with autotools....
- jnxx 6y agoJust to add, Guix configuration does not only look declarative - it uses a mostly functional language in a side-effect style to define the builds, in the same way as NixOS, just with a language which is established, well-supported, minimal, and elegant. One of the advantages is that this functional package definitions define very clearly what is provided by a package. It also works well for other languages like Rust or Clojure.