nixos-conf-editor
nixpkgs
nixos-conf-editor | nixpkgs | |
---|---|---|
7 | 975 | |
410 | 15,753 | |
8.3% | 2.8% | |
5.3 | 10.0 | |
3 months ago | 3 days ago | |
Rust | Nix | |
GNU General Public License v3.0 only | 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.
nixos-conf-editor
- AI roasts NixOS users
-
SnowflakeOS - Creating a GUI focused NixOS-based distro
Sounds a lot like nixos-conf-editor :) It allows for arbitrary nix code to be set for any option, and evaluates it to check for the correct type before setting it as the value in your configuration file
-
Nix Software Center: gtk4/libadwaita app store for NixOS
Actually already made a similar tool :) https://github.com/vlinkz/nixos-conf-editor
- NixOS Configuration Editor: A gtk4/libadwaita app to edit and manage basic configurations without (much) coding
-
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.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
nix-editor - A simple rust program to edit NixOS configuration files with just a command
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Nixos-Gui - Gui for Nixos package manager
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nix-gui - Use NixOS Without Coding
git-lfs - Git extension for versioning large files
Relm4 - Build truly native applications with ease!
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
nix-software-center - A simple gtk4/libadwaita software center to easily install and manage nix packages
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
system-updater - Systemd services for checking for and applying system updates.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.