It’s not a permanent one and it works for the time being, can’t see the reason for the downvotes honestly.
It’s just a bad idea in general. A better option would be to patch the binary to use 15. They both have the issue of forcing paru to work with a library it wasn’t explicitly designed for, but symlinking (or copying) 15 to 14 forces the hack to be “system wide” instead of restricted to a single binary
as well, your solution is “temporary” only if you remember to fix it, vs patching which is (by default) overwritten the next time paru is updated
it “works”, but it’s not something i’d recommend someone else do
I found a hack. Assuming you now have
libalpm.so.15, just make a copy of it and rename it tolibalpm.so.14:cp /usr/lib/libalpm.so.15 /usr/lib/libalpm.so.14Edit: It’s not a permanent one and it works for the time being, can’t see the reason for the downvotes honestly.
It’s just a bad idea in general. A better option would be to patch the binary to use 15. They both have the issue of forcing paru to work with a library it wasn’t explicitly designed for, but symlinking (or copying) 15 to 14 forces the hack to be “system wide” instead of restricted to a single binary
as well, your solution is “temporary” only if you remember to fix it, vs patching which is (by default) overwritten the next time paru is updated
it “works”, but it’s not something i’d recommend someone else do
Boy that’s… that’s one way to solve it I guess.
The redneck engineering equivalent in CS