rnix-parser
system-updater
rnix-parser | system-updater | |
---|---|---|
3 | 4 | |
339 | 27 | |
3.2% | - | |
0.0 | 1.7 | |
13 days ago | 4 months ago | |
Nix | Rust | |
MIT License | Mozilla Public License 2.0 |
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.
rnix-parser
-
auto update notifier & gui for non-tech users?
I definitely plan to support as much as I can, but there is definitely a level of complexity that can never be truly translated to a graphical tool. What I've found helpful during development for me is that I split the frontend GUI and the backed parser and editor into two projects (nixos-conf-editor and nix-editor), that way I could tackle a lot of the parsing and editing alone without worrying about specific GUI features needed (and use it for other projects). Later when I need some feature I add it to nix-editor. So far nix-editor supports simple attribute modification, array adding and popping, and recursive attribute definition and dereferencing. It's definitely not perfect by any means, but so far it's been enough for the projects I've been working on. I definitely need to credit any success I've had so far to the developers of rnix-parser which translates nix expression to easy to manage ASTs.
-
Advantages of flakes
I'm hopeful that with https://github.com/nix-community/rnix-parser being a thing now, we can get some better Nix tooling, particularly for stuff like linting and doc extraction.
-
The Curse of NixOS
Okay, yes, I agree with all of that. Flakes are kind of a module system, but having clearer semantics around functions and classes would definitely help with both code readability and producing better stack traces.
And a proper type system would be awesome.
Regarding docs, it is interesting that portions of the nixpkgs source do seem to have docblock-like comments above the functions, but AFAICT there's no formalized process for extracting or rendering those. Given that https://github.com/nix-community/rnix-parser exists, I wonder how big of a leap it would be to actually extract those, render them into rST pages, and generate a searchable Sphinx manual.
system-updater
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
pop-system-updater
- Do most folks have Automatic Updates turned on?
-
auto update notifier & gui for non-tech users?
The most I've heard of is the Pop! OS system updater (https://github.com/pop-os/system-updater) does support updating nix packages (see https://github.com/pop-os/system-updater/blob/master/daemon/src/package_managers/nix.rs). It would probably need some modification to work on NixOS though. Other than that I don't think any graphical package managers are being maintained, although I've been meaning to dive in and make one once I finish the first release of my configuration editor
- Rust projects to learn from?
What are some alternatives?
Nixos-Gui - Gui for Nixos package manager
launcher - Modular IPC-based desktop launcher service
supertux - SuperTux source code
nickel - Better configuration for less
cosmic-settings - COSMIC Settings
nix - Nix, the purely functional package manager
tiler - Generic tiling window manager library in Rust
nvd
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
nix-editor - A simple rust program to edit NixOS configuration files with just a command
nixos-conf-editor - A libadwaita/gtk4 app for editing NixOS configurations