niv
poetry2nix
Our great sponsors
niv | poetry2nix | |
---|---|---|
16 | 21 | |
1,456 | 726 | |
- | 6.6% | |
6.3 | 9.7 | |
about 2 months ago | 3 days ago | |
Haskell | Nix | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
niv
-
NixOS + Haskell best practices circa March 2023
niv
-
Pulling themes from a git project: the nix way?
Flakes work. An alternative is niv which was once popular and provides a good developer experience.
-
What are the biggest Pain Points with NIX? And what makes it worth the pain?
Essentially you can just think of it as a standardized default.nix/shell.nix with built-in Niv integration.
-
Our Roadmap for Nix
I agree that the FP part is not the only issue. It's that the community feels a bit more academic/I'll fix this for myself in the way that works best for me.
You can indeed achieve some reproducibility with Docker. It's tricky though, as you'd have to pin exact package versions of software. If you'd `FROM ubuntu:$VERION`, and would run an `apt-get update`, you're not guaranteed to get the same software.
Nix is like ZFS, as that it breaks the wall between two previously distinct area's. Those being building software, and installing/configuration software on your OS. It's quite different from the snapshot-everything methodology that Docker uses. Yeah, one can split in multi-stage images etc, but than you'll be keeping track of which dependencies need to be moved between the stages yourself, in a manner that cannot be abstracted away, so you're doomed to repeat the same patterns over and over again.
People also state that LVM + ext3 is more than sufficient compared to the complexity of ZFS. They miss out on the fact on how much more fine grained solutions are possible with ZFS.
I've used niv [0] before flakes arrived, and am actually still using that instead of flakes. The experimental nature of them has scared me away from them, as I'm not daily involved in this ecosystem at the moment.
[0] https://github.com/nmattia/niv#niv
-
Simplest way to set up neovim
You can use something like Niv to manage additional sources. I use it to fetch some Emacs packages, for example ligature.el. Then you update the package using $ niv update.
-
Unstable vs Stable channels
One thing that made this easier was switching from using Nix channels to explicitly pinning my dependencies with Niv. I honestly never fully understood how channels worked, and it's just much nicer to have everything specified in my Git repo. The exact commit of Nixpkgs that I'm using is in my sources.json file, so "reverting" just means checking out an older commit of my configs from Git then running nixos-rebuild switch. If I were redoing my dotfiles today I'd probably use Nix Flakes rather than Niv, but I suspect that Niv is still an easier option to get started with.
-
Remove unused niv packages
Does someone know of a way to remove unused pinned packages via [niv](https://github.com/nmattia/niv)?
-
How to downgrade single package?
Pin nixpkgs, and version control it. If you're using flakes, then just version control the flake.lock alongside your configuration. If you're not using flakes, you can use niv to easily pin nipxkgs, at the expense of some boiler plate.
- Compiling emacs is killing me
-
Ditch Your Version Manager
This... This is laughable. How do I install ruby 2.6.8? Oh, there's no ruby_2_6_8, because of course there isn't. And this could be difference between a secure system and all your base are belong to us.
And they call this reproducible builds?
And that's before getting into the ridiculous
--- start quote ---
All the software that we installed depends on the specific version of the nixpkgs channel that we installed on our system [whose only version is a commit hash in a git repo]
--- end quote ---
So you need an extra tool [2] for, quote, "painless dependencies for Nix projects."
Yes, sure. I'm definitely ditching my version managers in favor of this tool, that hasn't solved these issues in 18 years of its existence.
[1] https://search.nixos.org/packages?channel=21.05&from=0&size=...
[2] https://github.com/nmattia/niv
poetry2nix
-
Things I've learned about building CLI tools in Python
How about converting it to Nix derivation?
https://github.com/nix-community/poetry2nix
-
Poetry2nix: mismatch cryptography sha256 but unable to modify
This looks really strange because I do not know how to solve it and also because it looks like the sha256 that I am setting is not the one that Nix will match. I read also https://github.com/nix-community/poetry2nix/issues/413 but I was not able to solve the problem.
-
As if there weren't enough packaging tools already: mitsuhiko/rye: an experimental alternative to poetry/pip/pipenv/venv/virtualenv/pdm/hatch/…
There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)
-
Issue building pycairo in python flake
{ description = "Application packaged using poetry2nix"; inputs.flake-utils.url = "github:numtide/flake-utils"; inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; inputs.poetry2nix = { url = "github:nix-community/poetry2nix"; inputs.nixpkgs.follows = "nixpkgs"; }; outputs = { self, nixpkgs, flake-utils, poetry2nix }: flake-utils.lib.eachDefaultSystem (system: let # see https://github.com/nix-community/poetry2nix/tree/master#api for more functions and examples. inherit (poetry2nix.legacyPackages.${system}) mkPoetryEnv; pkgs = import nixpkgs {inherit system;}; python = pkgs.python310; pythonEnv = mkPoetryEnv { inherit python; projectDir = ./.; preferWheels = true; }; in { #packages.default = mkPoetryEnv { # projectDir = ./.; # python = pkgs.python310; #}; devShells.default = pkgs.mkShell { buildInputs = [pythonEnv]; packages = [ poetry2nix.packages.${system}.poetry pkgs.cairo pkgs.pkg-config pkgs.gobject-introspection pkgs.tk ]; }; }); }
-
Setting up Stabe Diffusion on NixOS
A cleaner way might be to use https://github.com/nix-community/poetry2nix which can load poetry.lock inside Nix. I still need to try it for torch, but it does seem like a clean way to use it.
- Ask HN: Is anyone successfully self-hosting Firefox Sync?
-
How do I install dependencies for a python application
The README for poetry2nix (https://github.com/nix-community/poetry2nix) seems to indicate that all extras should be enabled by default.
-
how to install Python packages not yet in the Nix repo?
if it's for a project you're working on, i'd recommend just using poetry2nix
- What is the point of containers in prod if one can use Nix everywhere?
-
Issue when installing python packages
poetry2nix is another popular option.
What are some alternatives?
leksah - Haskell IDE
mach-nix - Create highly reproducible python environments
update-nix-fetchgit - A program to automatically update fetchgit values in Nix expressions
flake-utils-plus - Use Nix flakes without any fluff.
ghcid - Very low feature GHCi based IDE
nixos-generators - Collection of image builders [maintainer=@Lassulus]
elm-make
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
hpc-threshold - Small utility for validating whether HPC result is above defined thresholds
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
ihaskell - A Haskell kernel for the Jupyter project.
nix - Nix, the purely functional package manager