[bravetraveler]

I was thinking/wondering this myself. Not to reinvent the wheel - more toss an idea around, but a 'venv for LD_PRELOAD' sounds like it'd deal with this pretty handily

Not... in a way I'd use as a distribution/release maintainer. Probably as an administrator [of my LAN]

[gabcoh]

Such things already exist. Eg. Appimage or even docker.

[lnxg33k1]

and even that has been managed to be split between snap appimage and flatpak :D

(sorry not meant to offend, long time linux day-to-day user here, but it was just ironic for me to point out fragmentation of fragmentation ^^)

[bravetraveler]

Right, but I don't really want to get into a distribution model - the hack suits me fine :)

More an exercise in curiosity than anything

Flatpak (or Snap, ew) probably deals with it fine today, Steam's there

[0x457]

That's Nix with extra steps.

[bravetraveler]

I specifically said I'm not really trying to solution this, lol. More toying with the LD_PRELOAD aspect than anything

Nix is neat, and I don't think I've used it enough to be too critical - but in some ways it feels like 'extra steps'

I wanted to make a 'reproducible' installation (ala kickstart, not strictly binary)... but it felt very much like distribution work; declaring dependencies and the like

[0x457]

Oh, nix is an extra mile. A lot could be improved, but that's what I'm using to deal with dependencies.

[bravetraveler]

Gotcha, I don't feel so floundering now!

I plan to spend more time with it, I see a lot of merit

The amount of control is great, but the docs could use some work. For my simple goals (install Sway, Ansible, some other things) it was a broadsword when I need a butter knife

[0x457]

What sold me on nix is home-manager and flakes: I can easily bootstrap my environment anywhere nix is available.

[never_inline]

There are tools which overwrite linked libraries, eg: chrpath.