niv
repology-rules
Our great sponsors
niv | repology-rules | |
---|---|---|
16 | 29 | |
1,456 | 101 | |
- | - | |
6.3 | 9.9 | |
about 2 months ago | 4 days ago | |
Haskell | Python | |
MIT License | GNU General Public License v3.0 only |
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
repology-rules
-
Could you theoretically use other package managers on void?
A lot, it's (also) a complete linux distribution. See https://guix.gnu.org/en/packages/ and for comparison with other distros: https://repology.org/ It looks like they entered the top ten since last time I checked.
-
what OS do YOU use, as an emacs user?
I'm having a hard time believing it, but apparently nixpkgs is larger than AUR per https://repology.org/?
- Common denominator when developing widgets
-
How to deploy my FOSS to Linux users / repositories?
Generally, the easiest thing to do is to do nothing - if your software is useful and people are using it, then packagers will show up. You can track what distros packaged your project on https://repology.org/.
-
Discover Slitaz, a 50MB Lightweight Desktop Operating System
I remember when the internet was smaller (20 years ago?) some people would have a comparison of different package managers for linux distros where they would dive in to examples and use. Anyway, this is a high level of package currency : https://repology.org/
The last distros I've used that didn't really have their own package managers were Slackware (it is just a tarball) and PuppyLinux (adopted from slackware or debian).
Anyway, Slitaz is here https://repology.org/repository/slitaz_cooking
-
The problem raised by Linus Torvalds on package management
You can basically install nix packages on every Linux and even MacOS. They are imo better developed and less error prone. You are guaranteed to never have dependency issues. The hashing scheme and idea of representing and building packages from derivation logic is spectacular design. The design of Nix inherently supports atomic upgrades and the likes of an immutable system. Also, afaik, it has the largest package availability currently (at least as many pkgs as Arch's) https://repology.org/
-
Nix (the package manager of NixOS that can be installed on other distributions like Flatpak) releases version 2.4
Yep, it's no. 1 on https://repology.org/
- Ask HN: What useful unknown website do you wish more people knew about?
-
Distros
Most have it on their website, but you can also check here
- Is there a website that has all the "apt install <app>" apps?
What are some alternatives?
leksah - Haskell IDE
nix-darwin - nix modules for darwin
update-nix-fetchgit - A program to automatically update fetchgit values in Nix expressions
bgart - Set classic art for GNOME background
ghcid - Very low feature GHCi based IDE
nixos-shell - Spawns lightweight nixos vms in a shell
elm-make
stylegan2 - StyleGAN2 - Official TensorFlow Implementation
hpc-threshold - Small utility for validating whether HPC result is above defined thresholds
nixos-generators - Collection of image builders [maintainer=@Lassulus]
ihaskell - A Haskell kernel for the Jupyter project.
jsmin - Javascript minifier