From: "Stefan Mühlinghaus" <"master..."@googlemail.com>
To: voidlinux@googlegroups.com
Subject: Libraries in program-packages?
Date: Fri, 16 Jan 2015 12:01:14 -0800 (PST) [thread overview]
Message-ID: <21529b03-5a50-4a33-bec5-1764559c7050@googlegroups.com> (raw)
[-- 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 --]
next reply other threads:[~2015-01-16 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 20:01 Stefan Mühlinghaus [this message]
2015-01-16 20:07 ` Juan RP
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21529b03-5a50-4a33-bec5-1764559c7050@googlegroups.com \
--to="master..."@googlemail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).