Potentially but it’s not always that simple. I’ve literally encountered this exact scenario. OldeShit needs libY 1.9 but pacman is on 2.2. Can’t downgrade because libY uses 10 different libs collectively in the depends tree that explicitly need 2.0 or higher. So you take a look at libY and OldeShit builds only to realise several functions that libY provide have been reworked or removed, making it incompatible with OldeShit. As such OldeShit doesn’t build.
As an aside, this is quite literally why Microsoft has several different VC Redistributables. To avoid this issue. But this also creates another issue. Lol.
Someone probably could. But not me. I am not a software developer, and being one should not be a prerequisite to using an OS, despite what the memes in this very group might lead one to believe.
can you not recompile the app to use the new lib?
that’s when you find out that the updated build environment is incompatible with the older libraries the project expected.
usually the only escape is docker, or containerization to be correct, just give the old app and old environment.
this wastes a lot of space though
Potentially but it’s not always that simple. I’ve literally encountered this exact scenario. OldeShit needs libY 1.9 but pacman is on 2.2. Can’t downgrade because libY uses 10 different libs collectively in the depends tree that explicitly need 2.0 or higher. So you take a look at libY and OldeShit builds only to realise several functions that libY provide have been reworked or removed, making it incompatible with OldeShit. As such OldeShit doesn’t build.
As an aside, this is quite literally why Microsoft has several different VC Redistributables. To avoid this issue. But this also creates another issue. Lol.
Someone probably could. But not me. I am not a software developer, and being one should not be a prerequisite to using an OS, despite what the memes in this very group might lead one to believe.