Dependencies:
Old ass library version from 2004
apt/dnf/pacman: package not found
library package was last available 15 years ago before it was dropped to move to the next legacy version
App package was available right up until last year until it was dropped for development inactivity
Absolutely no one has a compiled version of old ass library
Attempting to compile old ass library results in 30 other old ass package dependencies
How in the actual world was the maintainer compiling this up to last year
It worked on their machine
They have old/orphaned dependencies on their machine. It’s hanging on a by thread. They have no idea the packages have disappeared years ago. The house of cards is a bit flip away from collapsing.
Hahah I say this all the time.
Why docker was created be like
Does docker solve this problem?
Why even use releases? Everyone can build everything for themselves. ‘Normal Users’ are just lazy, everyone wants to know how every piece of software is built for their system, it’s not like they have other stuff to do.
Ah the Linux help desk where you get helpful directions like “You have a problem with your dual monitor setup in your naively installed Ubuntu setup? Have you considered installing a rust micro kernel from an abandoned GitHub repo? After cherry picking some patches from a mailinglist? Also boon plep Ubuntu looser.”
yay <package name>
There is a 99% chance it’s in there, and there is an 80% chance it uses the latest version/git HEAD
Yay?
yay, a utility to access the AUR, where users share build scripts instead of binaries. It’s just one step abovecurl | sudo shin terms of security.Except it automates the steps you’d have to take to inspect and edit the script, if needed. Also, PKGBUILDs are much nicer to read than just plain install scripts. And, of course, it actually builds a package, which is then installed, so it’s not only tracked but can be updated like the rest of the system.
I don’t think the aur can switch the delivered script whether you are piping it into sh or not.
Hey, get your Gentoo propaganda out of here.
deleted by creator
Casual Linux things that get normal people running from the os in fear.
Package version 0.01: Built with libraries abc version 2, def version 0.1 and ghi version 7.2.2
Your system has requirements: abc version 2, def version 0.2 and ghi version 8.0.0
Package version 0.02: Requires abc version 3, def version 0.2 and ghi version 8.0.1
You realise that those differences in version would mean that you would have to basically recompile (then debug and recompile) your entire operating system with the three upgraded packages, and deal with a full cascade of dependencies, not just the package you really want to compile, OR basically sit down and rewrite Package 0.02 from the ground up using older libraries than it was originally written for.
You decide to make do with the old version of the package.
Can you not build it in a venv to not mess with your system packages?
That would only solve it for python, not for say c shared libraries. For that you’re in nix land or guix or if you hate yourself containers.
I’m in nix land so I just write nix derivations so not a big deal having many versions of the same thing at once.
And halfway through the compile, it fails.
“Tomorrow”
There’s so much wrong with this question.
- things people ‘must’ have are usually worthless junk like ‘dark mode’.
- updates people want in mainstream can sometimes break compatibility with no “just make it work” switch to disable the breakage. When this isn’t a red flag, that makes me sad and worried for the idiot in front of me.
- and then I’m no longer tolerant of the indolent writing error in the sentence.
Really, it’s a combination of all three of those things, and more, that prevent the incrementing of the one number in the git project that would invoke the package run and drop a new package in about 2 minutes. It’s so hard.
