nixpkgs VS nix-gui

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...

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...

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

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...

True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)

It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.

That is the problem.

We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.

I think whateveracct was referring to is this link:

https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...

What that file is doing, is building a package, and it essentially is a combination of what Makefile and what RPM spec file does.

I don't know if you're familiar with those tools, but if you aren't it takes some time to know them enough to understand what is happening. So why would be different here?

#!/usr/bin/env nix-shell #! nix-shell -i bash #! nix-shell -p sops #! nix-shell -I https://github.com/NixOS/nixpkgs/archive/refs/tags/23.05.tar.gz source config.sh "$@"

NixOS just got tabbyml[1] which is built on llama-cpp. Working on systemsd services the weekend and updating latest tabbyml release which supports rocm in addition to cuda

[1] https://github.com/TabbyML/tabby

[2] https://github.com/NixOS/nixpkgs/pull/291744

This is pretty close https://github.com/nix-gui/nix-gui

Nix based aiming at beginners. If it combines/works with https://github.com/nix-gui/nix-gui, then an amazing distro may be created. It would be user friendly, but also extremely powerful, allowing basically everything to be configured via the gui. Both softwares are alpha state, but I am excited to see what they bring.

Maybe https://github.com/nix-gui/nix-gui? I dunno if it can do userspace config though.

Would it make sense to integrate something like nix gui into this?

I remember when I first started using NixOS, as a confused beginner I tried to find a graphical application to manage and edit my configuration. I stumbled upon Nix-Gui, however, I didn’t really like the look, it crashed a fair amount, and I never really figured out how to use it. That said, their idea and all of the hard work they put into their project inspired me to make a similar application that focuses more on simplicity and ease of use.

I was wondering if you are aware of https://github.com/nix-gui/nix-gui and how your tool compares to it

There is also a GUI in development, hopefully it will help casual users in the future.

There's https://github.com/nix-gui/nix-gui for a gui like experience.

Configuration language usage: Probably a major win for programmers, but a major negative for non-programmers. However, nix-gui has shown that there's potential for gui-based nixos configuration. And this might one day be extended to use as part of the graphical installer. https://discourse.nixos.org/t/why-is-there-no-installer-for-nixos/16644/21. Since nix can be serialized and deserialized to json, there's actually a fair amount of interoperability able to be done to manipulate nix configuration using existing libraries.