I have stopped installing stuff from apt and thankfully my system never breaks now.
nix is a package manager, that is going to install packages in its own way.
the discussion here is about bedrock linux, that answers a specific question: what if, for any reason, you need packages from two (or more?) specific, very different distros?
what if you need packages from BOTH ubuntu and rhel?
to that question, the answer is not "install nix".
which is really bad because i see the value in nix, it's a very nice system, but nix fanboys are getting really annoying with mentioning nix in any discussion where package management is even tangentially related. it kinda reminds me of that old video about mongodb being webscale.
Nix is highly relevant because it solves that case: you can run Nix on any stable distribution like Debian, and the Nix package repository contains a very large amount of mostly up-to-date software, similar to the Arch+AUR repositories.
Another problem it solves more generally is getting access to a large repository of maintained packages from a base system that only has a small repository, even if those packages are up-to-date.
Both of these are reasons you might use Bedrock, so it doesn't seem off-topic.
With nix you can install packages with different versions, you can also install old packages by going back in nixpkgs history and building the package.
Nix being source based means you can install any software package as long as you have access to it's source.
Ofcourse some of this is possible with other systems too but the nix ecosystem makes it far easier to build packages in different languages.
In short nix can treat the disease (missing different versions of packages in distros) instead of treating the symptoms (installing packages from different distros)
being lazy I've never considered the NixOS packing. it's a steep learning curve and also "old dog, new tricks". I'm sure it's awesome to use professionally but unless I see a commercial reason to use and apply it on the job, I won't bother (not because of lazy but because of many other competing things I want to do).
Most of time it's 5 commands tar -xf code.tar.gz && cd blah && ./configure && make -j5 && sudo make install
Very early Bedrock Linux prototypes were exactly this; including the choice of schroot. Bedrock could be correctly described as taking this idea and running with it, trying to stomp out as many of the "you do have to"'s and "except"'s as it can.
> Those solutions are hard to set up than bedrock, but they also do not have special filesystem magic,
I think a fair description of the trade-off between Bedrock and the two alternatives you've laid out should mention the breadth of functionality Bedrock offers they do not. This includes but is not limited to:
- Shell tab completion. For example, Debian's zsh can tab-complete Arch Linux's pacman
- Init systems. For example, one could run Void Linux's runit init, install Arch Linux's systemd, and reboot into systemd.
- Kernels. One could run Arch's kernel, install Debian's, update the bootloader configuration, reboot, and select Debian's kernel.
et al.
I expect, if you think about it long enough, you could see some ways schroot with things like /home mapped in could be extended to cover those use cases. If you pursue those, you'd end up recreating Bedrock.
> so I bet they are much easier to debug.
I am doubtful any user which understands setup schroot you described, who also takes the time to familiarize himself or herself with Bedrock, would have comparative difficult debugging a Bedrock system.
The primary concern I personally hold is in Bedrock's code to bootstrap parts of other distros, which does not currently verify the initial set of files used. I am hoping to address this with Bedrock's next major release (0.8.X) [2].
When Bedrock is far enough along that the architecture/code churn slows, I plan to seriously investigate the possibility of independent security reviews. For the time being, if someone claims heightened security needs, I usually redirect them to Qubes OS [3].
[0] https://bedrocklinux.org/faq.html#security. [1] https://github.com/Duncaen/OpenDoas/releases/tag/v6.8.1 [2] https://github.com/bedrocklinux/bedrocklinux-userland/issues... [3] https://www.qubes-os.org/
I learned something new. I only knew about chroot. If I'm understanding, schroot is chroot for normal users?
For the less extreme case, when you want mostly one distro, but also a few packages from another one, there is “alien” [0] which converts between different package formats. It sometimes needs help with system integration or dependencies, but occasionally “just works”
For a more extreme case, there is a schroot (or a docker container) with /home, audio and X mapped in. Works surprisingly well for desktop apps, like those embedded IDEs which require a specific Linux distribution you don’t want to run. You do have manage desktop integration (menu items, file associations) yourself though.
Those solutions are hard to set up than bedrock, but they also do not have special filesystem magic, so I bet they are much easier to debug.
[0] https://manpages.debian.org/unstable/alien/alien.1p.en.html