[iamcreasy]

> Most Linux package managers cannot separate user-installed packages from system packages.

What is the use case when someone would want to differentiate system/user installed package? Isn't it good things that they are the same - meaning once something is install - it is there regardless of how it got here.

[wolrah]

Two reasons come to mind for me:

1. It's very common, especially in certain ecosystems like Python, for the system to depend on old versions of things in such a way that updating to modern versions will break your entire system, while at the same time you want to run something at the user level that depends on a newer version. The solutions to this are usually ecosystem specific and often annoying to use for someone who just wants to run a program (again a great example being Python venvs, which at this point have decades of tooling built up around trying to make it less annoying to deal with).

2. For "cattle" systems having everything installed at the system level is generally not too much of an issue, but for "pet" systems where the user might be experimenting with things it's really nice to be able to install stuff in a way that doesn't affect anything outside of your user account even if it's also available at the system level. The computers that I personally operate from on a daily basis tend to build up a lot of crap I used once over time and removing it without just backing up my stuff and nuking it all can be a major pain.

[giancarlostoro]

Honestly for python just using uv is enough, not only does it handle virtualenv for you, it will also install the necessary python version you need locally.

[curt15]

Devs shouldn't need root access to install tooling or dependencies for a project.

Mixing user and system software is like having Photoshop and all of your games install their files directly into the Windows directory.

[selicos]

In my current use case I'm setting up a new Ubuntu server for hosting LLMs. I didn't take notes when setting it up last time around but want to document exactly what was required to pass on to coworkers trying something similar. I don't know what packages I installed to get the minimalist setup working vs what is installed by default. I'm tempted to nuke and redo with notes but I'm sure there is a better method of tracking down what I deployed to get to the current state.

...or not, and this is why HomeBrew exists and I need to learn it or ansible/etc.

[michaelmrose]

NixOS seems ideal for this.