nix-update
napalm
nix-update | napalm | |
---|---|---|
5 | 2 | |
393 | 101 | |
- | 0.0% | |
8.2 | 6.1 | |
8 days ago | 5 months ago | |
Python | 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.
nix-update
-
Accessing contents of non-flake repo input to a flake?
You should instead use the regular fetchGit, fetchFromGitHub etc. fetchers in fairly vanilla code, and yes, that often means dealing with checksums in some form. If you truly just want to yeet the latest revision into place no matter what it is, there are ways to automate that still, such as berberman/nvfetcher, or Mic92/nix-update.
-
Will you move from Packer to Lazy ?
Yes, however one downside is that, afaik, the inputs are downloaded eagerly, not lazily. Alternatively there are things like nix-update and nvfetcher.
-
How easy would it be to make Nix packages similar to -git packages of the AUR?
or https://github.com/Mic92/nix-update
-
Beat way to update an outdated package?
You can also use https://github.com/Mic92/nix-update with a nixpkgs git clone.
-
NixOS 21.05 Released
I run [nix-update](https://github.com/Mic92/nix-update/) to update stuff. If you want to package something new, first identify the programming language/buildsystem the project is using and than look for a similar project in nixpkgs.
napalm
-
niv, naersk, napalm: moving on
I created https://github.com/nmattia/napalm/issues/34 and https://github.com/nmattia/naersk/issues/183 to move them to nix-community
-
NixOS 21.05 Released
Sure. NPM is the easy case because the package-lock.json file can easily be read by Nix and contains hashes for all of the packages. This means that simply be importing the file into Nix you can have a reproducible build. No Nix-specific maintenance required.
In the linked case I use this library to manage that https://github.com/nmattia/napalm (in that example I use master but for production I would pin a version). It simply parses the package-lock.json, downloads the packages and uses npm to build the node_modules folder. It also provides some convenient functions for building packages with "bin" files or just linking node_modules inside a build.
Note that this is more for project development. It doesn't use the "system" packages (intentionally) for Node, it fetches whatever versions you have specified from NPM. Nix will only provide the "native" stuff like Node and NPM themselves and any native libraries.
What are some alternatives?
LazyVim - Neovim config for the lazy
nixGL - A wrapper tool for nix OpenGL application [maintainer=@guibou]
nixos-generators - Collection of image builders [maintainer=@Lassulus]
nix - A declaratively managed computing environment for rraval
flake-utils-plus - Use Nix flakes without any fluff.
naersk - Build Rust projects in Nix - no configuration, no code generation, no IFD, sandbox friendly.
nix-bundle - Bundle Nix derivations to run anywhere!
nixos-shell - Spawns lightweight nixos vms in a shell
archbox - Easy to use Arch Linux chroot environment with some functionalities to integrate it with your existing Linux installation. Mirror of https://momodev.lemniskett.moe/lemniskett/archbox
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nix-processmgmt - Experimental Nix-based process management framework