DryTomatoes

joined 11 months ago
[–] [email protected] 1 points 10 months ago

Coming from other languages I find the async by default thing annoying but I fully understand it's necessary for web sites to render in real time.

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago)

Unless she uses Peacock. They seem to be the only streamer that's clinging to the 15 year old idea of just not supporting Linux.

[–] [email protected] 6 points 10 months ago

I've used a lot of Ubuntu over the years starting on 9.04. Let me tell you the six months releases are ass and always have been.

Also I'm switching to Debian.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

I hope someone who has more info comes along. It might be time for you to make a new post though since we're getting to the heart of the problem now.

Also it will be a lot easier for people to diagnose if you are specific about which programs you are failing to install.

I've only experimented with Python in docker and it gave me a lot of headaches.

That's why I prefer to pip install things inside venvs because I can just tar them myself and have decent portability.

But since your installing files across the system I'm not sure what the best solution is.

[–] [email protected] 2 points 11 months ago

Thanks for the info! I'm definitely gonna look into flatpak.

I built nodejs from source yesterday and it took forever. I'd definitely prefer something huge like that in a flatpak.

[–] [email protected] 2 points 11 months ago (2 children)

This method should work with any command that's installing files on your disk but it's probably not worth the headache when virtual environments exist for python.

[–] [email protected] 8 points 11 months ago

Agreed. I hate anything auto updating on it's own because changes can break or remove features at any time.

[–] [email protected] 2 points 11 months ago (1 children)

Any POSIX compliant system as far as I know.

[–] [email protected] 19 points 11 months ago* (last edited 11 months ago) (10 children)

I did Linux From Scratch recently and they have a brilliant solution. Here's the full text but it's a long read so I'll briefly explain it. https://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt

Basically you make a new user with the name of the package you want to install. Login to that user then compile and install the package.

Now when you search for files owned by the user with the same name as the package you will find every file that package installed.

You can document that somewhere or just use the find command when you are ready to remove all files related to the package.

I didn't actually do this for my own LFS build so I have no further experience on the matter. I think it will eventually lead to dependency hell when two packages want to install the same file.

I guess flatpaks are better about keeping libraries separate but I'm not sure if they leave random files all over your hard drive the way apt remove/apt purge does. (Getting really annoyed about all the crud left in my home dir)