It sounds like you might not be using a distro that comes with the right development toolkit and resource information.
Dependencies are always known.
slackbuilds.org
Every SlackBuild specifies them.
Multisbo recursively handles them.
github.com/annemedia/multisbβ¦
Compiling your own software, including dependencies, is very easy with the right OS and the right tools. And not as time-consuming as it may seem. You run it, forget about it, and when it's done, you install it and use it.
I compile & deploy my custom & native CPU-optimized kernel in a matter of hours, and only recompile if a security upgrade is worth the effort.
I compile the KDE suite with native CPU optimization overnight, and install it all in a one-liner, and only upgrade major versions.
Any custom software I need at the top is a one-off effort, unless I feel like upgrading.
What most Linux users don't understand is why they should do it themselves. The performance and stability benefits & time I gain far outweigh the extra "inconvenience" of DYI. Frankly, it's no inconvenience at all.
The package managers are the root of all evil.
And if anyone tells me Slackware isn't for newbies. Please, I knew nothing about Linux and compiling software, but I was the first distro I picked decades ago.
I managed just fine back then without any AI assistance by reading forums. My parents used Slackware because once set up, it just works.
There's no excuse now, while AIs can guide anyone and quickly resolve issues.
And there's nothing like a system you make your own and never goes bust, and even if it were, you know how to fix it.