How does arch handle multiple versions of a lib

chrisdb · 2019-07-09 06:06:32

Hi,

I was wondering how arch handles packages which require multiple versions of the same library. Like f.e. package one requires aLib version 1, but package two requires version 2 of aLib.

I know arch tries to keep all packages up-to-date, but not every app is so frequently updated.

Are these compiled with specific path parameters, or is there some other magic playing?

Thx

Scimmia · 2019-07-09 06:08:51

Everything is rebuilt against the new lib and the old one goes away.

chrisdb · 2019-07-09 06:15:33

Scimmia wrote:

Everything is rebuilt against the new lib and the old one goes away.

So an app which requires an older version of a lib, is rebuilt with the new one? What does this mean, do you change the source code then to use the new version?

seth · 2019-07-09 06:54:40

an app which requires an older version of a lib

What do you mean by "requires"?

Typical breaks are ABI ones, ie. recompling/linking does the job. If the lib is API incompatible it will come in different major versions and you have to install and explicitly link both.
If it's a binary only executable, you'll have to eg. run a script to ensure to LD_PRELOAD the required (typically local) shared object.

Please reveal your specific concern/case rather than asking a generic question about "what does one do if things don't match" - there's a gazillion ways for mismatches (or to deal w/ them, eg. with versioned symbols)

Arch Linux

#1 2019-07-09 06:06:32

How does arch handle multiple versions of a lib

#2 2019-07-09 06:08:51

Re: How does arch handle multiple versions of a lib

#3 2019-07-09 06:15:33

Re: How does arch handle multiple versions of a lib

#4 2019-07-09 06:54:40

Re: How does arch handle multiple versions of a lib

Board footer