void-packages VS nixpkgs

I was looking for a lightweight OS to run on old Asus Eee PC 1005 HA, which uses a 32-bit Intel Atom N270 processor. I installed Void Linux (https://voidlinux.org/).

I may give DSL 2024 a try and see how it compares.

Linux Void

My computer is running Void Linux and it has only a wired network connection. I can hook up my phone for USB tethering if I need to connect to the WiFi of the ESP32. How do I update the software without downloading some shady programs from filesharing site links on my system? I have the Arduino IDE and the esptool.py script installed.

Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software".

Some distros like Void seem to patch this out.[1]

From mandoc/mdocml's mandoc_char(7) [2]

In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus.

Which is the common-sense thing to do.

Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this.

In general the amount of wankery of "the correct hyphen" is staggering.

[1]: https://man.openbsd.org/mandoc_char

[2]: https://github.com/void-linux/void-packages/blob/20c66829134...

So I was about to configure a new Archlinux build on my PC and came across Void Linux. I had already read about it a year ago but never researched it in depth. I know that is a Linux distribution made from scratch, with a different package manager and so on. Void Linux users or people who have tried it, what are your thoughts on it? Do you think the PM is easy to use? what about updates and bugs? what desktop or Tilling Window Manager do you use? could you tell me about it?

Good news about dbus-next: https://github.com/void-linux/void-packages/pull/46760

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