Libraries in program-packages?

Libraries in program-packages?

[Stefan Mühlinghaus]

[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]

I am currently in the process of creating a package for a closed-source 
binary program that depends on several older library versions. What is the 
preferred way to deal with this problem? I would rather not put an older 
version of the libraries as independant packages into the repositories only 
to get this one package working (that should be recompiled and linked 
against current versions anyway).

My current approach is to build the libraries with the program, install 
them into a library-subfolder and run the program with an appropriate 
LD_LIBRARY_PATH. Is this acceptable? Are there other alternatives?

Another problem is that the automatic ELF dependency detection process 
fails since the required libraries are not provided by any package. Is 
there a way to circumvent these errors?

[-- Attachment #1.2: Type: text/html, Size: 861 bytes --]

Re: Libraries in program-packages?

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 510 bytes --]

Hi,

- Adding the missing shared libraries to the package into a private 
directory and using LD_LIBRARY_PATH is perfectly fine,
  you can create a wrapper to set up this.

- Another way would be using `patchelf` to add a RPATH to the binary, this 
way you wouldn't need to use LD_LIBRARY_PATH.

To make `xbps-src` ignore the unmet shared libraries you can set 
`allow_unknown_shlibs=1` in the template to ignore them.

Either way you'll have to add the missing shared libraries into the package.

[-- Attachment #1.2: Type: text/html, Size: 550 bytes --]