I'm not sure that would cause any suffering in NixOS other that running out of disk space; one of the big claims of nix is that it happily lets you install whatever you want without conflicts. Although they also have a somewhat different idea of what "install" means; you might have to still put in some work to surface as many programs as possible to a single shell's PATH.
Installing Every Arch Package
61–70 of 90 posts
Re: Installing Every Arch Package
#62Re: Installing Every Arch Package
#63> Install every package of a different distro? In particular, I’d like to see someone do this for Ubuntu, Debian, and NixOS and watch them suffer. This was painful enough. I'm not sure that would cause any suffering in NixOS other that running out of disk space; one of the big claims of nix is that it happily lets you install whatever you want without conflicts. Although they also have a somewhat different idea of wh…
They mount a 1TB volume with all packages preinstalled
Re: Installing Every Arch Package
#64Earlier quoted context omitted.
Is this a real problem?
It's only a matter of time. Linux really only has a good malware track record due to lack of popularity.
These mechanisms for filtering packages are normally not present on systems that are plagued with malware.
Re: Installing Every Arch Package
#65For clarity, Arch has about 10k packages, AUR has around 60k packages. I believe this post is "just" about the 10k.
> I’d like to see someone do this for Ubuntu, Debian, and NixOS and watch them suffer.
Speaking for NixOS:
I have. I would sometimes do a nixpkgs-review[1] of the mass "rebuild" PRs for Nixpkgs[2]. Hard to know how long it took to build as I would just let it "cook" on my build server while I did other things. The other thing is that nix gives unique names to all built packages and utilizes "maximal sharing" thereof, so everything gets memo-ized[3] on future runs.
The scale of the official nixpkgs repository is 4-6x greater than that of Arch (AUR is the user repository). 9.6k Arch packages vs 59.4k Nixpkgs packages according to repology[4]
Lastly, installing packages in nix is different. Everything goes into the nix store, which is relatively "inert". I don't need to worry about "hooks" or stateful logic being executed affecting my system. "But then how do you create services and other meaningful abstractions needed to make an OS? I thought NixOS was a distribution" It is, and it's down through NixOS modules[5] in the form of a configuration.nix. The NixOS modules can compose the verticals in my system to deliver something coherent and amazing.
Server used:
OS: NixOS 22.05 (Quokka) x86_64
Kernel: 5.10.91
CPU: AMD Ryzen Threadripper 3990X (128) @ 2.900GHz
Memory: 125913MiB / 257687MiB
[0]: https://www.reddit.com/r/linux/comments/shxq12/comment/hv5by...
[1]: https://github.com/Mic92/nixpkgs-review
[2]: https://github.com/NixOS/nixpkgs/pull/144730#pullrequestrevi...
[3]: https://en.wikipedia.org/wiki/Memoization
[4]: https://repology.org/repositories/statistics/newest
[5]: https://nixos.wiki/wiki/ModuleRe: Installing Every Arch Package
#66Fun stuff. Reminds me of one former coworker, which didn't like me introducing FreeBSD. So he started installing all ports packages.. only to say the following morning: Look it's broken! ( disk was obviously full and this plot was irrational to people with some common sense ).
"Nice" former coworker...hope you found your way to freebsd anyway :)
Re: Installing Every Arch Package
#67Re: Installing Every Arch Package
#68Can anybody tell me which terminal is next to cool-retro-term (on the right) in this image? https://ta180m.exozy.me/images/bloated-kde.webp
Regardless, if you want a nice terminal that isn't retro shaded and has zero UI cruft like tabs, menus, etc. check out Alacritty.
Re: Installing Every Arch Package
#69> Now is this useful? The short answer is no. The long answer is also no. I can think of exactly zero uses of this experiment (and I must be pretty crazy for doing it). Well, at the very least it's a very computationally expensive test that managed to catch a few packaging bugs.
Even today it's kind of a headache to install packages on machines with no Internet access, usually the easiest solution is to download everything and setting up a package repo on the LAN.
If you want real fun, try setting up a nontrivial node.js project without direct Internet access.
Re: Installing Every Arch Package
#70'The OS: Oh you have three versions of Python, let's use the earliest version and make your program insecure'