From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.43.99.202 with SMTP id ct10mr14375166icc.29.1421438477160; Fri, 16 Jan 2015 12:01:17 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.82.209 with SMTP id h75ls1549986qgd.32.gmail; Fri, 16 Jan 2015 12:01:16 -0800 (PST) X-Received: by 10.140.108.166 with SMTP id j35mr32102qgf.18.1421438476903; Fri, 16 Jan 2015 12:01:16 -0800 (PST) Date: Fri, 16 Jan 2015 12:01:14 -0800 (PST) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux@googlegroups.com Message-Id: <21529b03-5a50-4a33-bec5-1764559c7050@googlegroups.com> Subject: Libraries in program-packages? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1128_1095568207.1421438474117" ------=_Part_1128_1095568207.1421438474117 Content-Type: multipart/alternative; boundary="----=_Part_1129_690065671.1421438474117" ------=_Part_1129_690065671.1421438474117 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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? ------=_Part_1129_690065671.1421438474117 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
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?
------=_Part_1129_690065671.1421438474117-- ------=_Part_1128_1095568207.1421438474117--