Nix ecosystem introduction ("Talk at my company")

Declarative package management for normal users

What is the relationship between Disnix and NixOps?

NIX + BAZEL = FULLY REPRODUCIBLE, INCREMENTAL BUILDS

Web Hosting with IPFS and Nix

How we use Nix at IOHK?

Why is rec needed here, and not in the example under 2.6.1?

Based on what I saw with other examples, rec is usually included when a_package.override is used inside packageOverrides. But why?

The entire chapter 3 is worth reading. Great resource on what a package (or more broadly, a component) is in regards to Nix.

Specifically "3.1 What is a component?"

There is no officially prescribed reading order of the Nix manuals, but it's safe to say that one should start this, the Nix manual. Then it would be prudent to briefly describe what a package is in the context of Nix and/or (at east) link to the definition.

I like how Dolstra's thesis has an entire section on the topic (that is, on the more general concept of components).

It is clear now that there can be multiple versions of the same package in the store, but how does one call them (e.g., if is an executable application)? Simply by using the full Nix store path (and create and manage one's own symlinks, with stow or manually)??

haskell-overridez is a tool and library of nix functions that simplify the use of overrides while developing haskell projects with nixpkgs.

A nix-based Haskell project manager

Eelco Dolstra's seminal paper

"fixed-point", "fix point" seems to be most important concept in Nix, because overrides, overridePackages, overlays are built using it.

• Nix Pill - Chapter 17. Nixpkgs Overriding Packages (the first place I saw this concept properly described)
• Nixpkgs issue - Add pkgs.overrideWithScope#44196 (best high level summary of Nixpkgs ever read)
• How to Fake Dynamic Binding in Nix
• Comment by zimbatm on NixOS Discourse
• nixpkgs/lib/fixed-points.nix

• [Nix-dev] Introducing Nixpkgs Overlays
• Video - Initial announcement of overlays by Nicolas B. Pierron (nbp)
• Overlays implementation by Nicolas B. Pierron (nbp)
• https://nixos.wiki/wiki/Overlays
• Gabriel439/haskell-nix issue #58
• NixOS: The DOs and DON’Ts of nixpkgs overlays
• Nix overlays and override pattern Stackoverflow thread

Should packageOverrides be deprecated in favor of Overlays?

• Nixpkgs issue - Deprecate packageOverrides? #43266
• Nixpkgs pull request - [WIP] Deprecate packageOverrides #43560

Where is buildEnv documented?

• How buildEnv builtin function works? Stackoverflow thread
• mkShell vs. buildEnv?
• NixOS Wiki, Documentation Gaps, section What's the relationship between nix-env and buildEnv
• How to copy a nix-env profile using nix-copy-closure?
• https://news.ycombinator.com/item?id=11803558

Find out where stdenv.lib functions are documented.

builtins.elem x xs

Return true if a value equal to x occurs in the list xs, and false otherwise.

builtins.parseDrvName s

Split the string s into a package name and version. The package name is everything up to but not including the first dash followed by a digit, and the version is everything following that dash. The result is returned in a set { name, version }. Thus, builtins.parseDrvName "nix-0.12pre12876" returns { name = "nix"; version = "0.12pre12876"; }.

What is a package in this context? That is, the callback's pkg parameter. Is it a derivation?

If I understood it correctly, whenever referencing other packages as inputs, those are actually derivations, that are just attribute sets.

Here's a Rolling Stone article on the matter.

His Wikipedia page is here.