nix-update
nix
| nix-update | nix | |
|---|---|---|
| 5 | 2 | |
| 393 | 12 | |
| - | - | |
| 8.2 | 7.9 | |
| 8 days ago | 2 days ago | |
| Python | Nix | |
| 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.
nix
-
NixOS 21.05 Released
I was able to make the switch over cold turkey after ~9 years of ArchLinux.
By sheer happenstance, I blogged earlier this week about one particular killer feature that doesn't get enough air time: https://news.ycombinator.com/item?id=27344677
My not-flake-yet configuration can be found at https://github.com/rraval/nix
-
Nix solves the package manager ejection problem
> How do NixOS users typically manage software that is not a Nix package
By writing a Nix package for it (I don't mean for this to sound flippant, tone is a bit hard to convey over text).
For example I have this alpha quality rust binary that I'm developing but I also want a stable version installed at the OS level. I write a Nix package and simply compose it into my overall NixOS configuration alongside the more official Nixpkgs: https://github.com/rraval/nix/blob/master/git-nomad.nix
> like a source code tarball where you would traditionally run configure && make && make install?
Nix has a bunch of defaults that make a conventional package like this straightforward.
Here's a package for a vanilla C binary + library that does the `autoreconf && ./configure && make && make install` dance: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/secu...
It's almost a little misleading because the actual steps are largely inherited from the defaults, you can read more about `stdenv.mkDerivation` here: https://nixos.org/guides/nix-pills/fundamentals-of-stdenv.ht...
What are some alternatives?
LazyVim - Neovim config for the lazy
napalm - Support for building npm packages in Nix and lightweight npm registry [maintainer @jtojnar]
nixos-generators - Collection of image builders [maintainer=@Lassulus]
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
flake-utils-plus - Use Nix flakes without any fluff.
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container
nix-bundle - Bundle Nix derivations to run anywhere!
nixGL - A wrapper tool for nix OpenGL application [maintainer=@guibou]
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
runix