EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Aug 5·5 min read
Nix Overrides That Expire Themselves
TL;DR
Nixpkgs now supports self-expiring overrides for Haskell packages, allowing developers to manage dependencies more effectively. This feature helps prevent redundant overrides when updating package versions.
✦ Why It Matters
Start using self-expiring overrides in Nixpkgs to simplify your dependency management today.
Key Takeaways
- Use self-expiring overrides to manage package versions effectively.
- Implement version checks in flake.nix for cleaner configurations.
- Apply this pattern to other overrides, like broken packages.
- Regularly review warnings to maintain up-to-date dependencies.
How It Works
The self-expiring override mechanism uses a function in flake.nix that compares the required package version with the version available in nixpkgs. If the available version meets or exceeds the required version, a warning is issued, prompting the developer to remove the override.
This is done using the lib.versionAtLeast and lib.warnIf functions, which streamline the process of managing package dependencies.