From: Maxime Devos <maximedevos@telenet.be>
To: 22138@debbugs.gnu.org
Subject: bug#22138: Search paths of dependencies are not honored
Date: Sat, 22 Jan 2022 22:27:15 +0100 [thread overview]
Message-ID: <e3960b96e782b5d01c93a8615e4f76463bb55682.camel@telenet.be> (raw)
In-Reply-To: <87bn9yk5mf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hi,
On second thought, honouring search paths of dependencies
(filtered by looking at the references?) would solve much more problems
than it could create -- a theoretical ‘problem’ is that more
environment variables than strictly needed might be defined (see e.g.
the wrap-program example) but it doesn't seem that it would create
problems in practice.
There's a limitation to keep in mind though: static libraries.
Suppose we have a static library variant curl/static tht links against
openssl:static. Then due to the static linking, curl won't keep a
reference to openssl:static (*), so there won't be a SSL_CERT_DIR/FILE
search path.
(*) Actually, that might wrong, libcrypto.a keeps a reference to
/gnu/store/plr00nij45964cyy7sfcg5rcsi8hks0h-openssl-1.1.1l.
For some examples in the wild where this kind of propagation(*) of
search paths is useful: all packages using ncurses (TERMINFO_DIRS),
openssl (SSL_CERT_DIR/SSL_CERT_FILE), all packages using glibc
(GUIX_LOCPATH) -- basically all software(!).
(*) it's not propagated-inputs but the concept doesn't seem completely
unlike.
As such, I agree with the concept (notwithstanding the previous mail I
sent), with the caveat that I haven't investigated the implementation
or tested it.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-01-22 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 9:36 bug#22138: Search paths of dependencies are not honored Ludovic Courtès
2019-08-01 20:12 ` Julien Lepiller
2019-08-05 16:23 ` Mark H Weaver
2019-08-05 16:31 ` Julien Lepiller
2019-08-23 14:42 ` Ludovic Courtès
2019-08-24 13:52 ` Ludovic Courtès
2019-11-26 12:00 ` Julien Lepiller
2022-01-14 19:48 ` bug#22138: Should search paths of dependencies be honored automatically? Maxime Devos
2022-01-22 21:27 ` Maxime Devos [this message]
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=e3960b96e782b5d01c93a8615e4f76463bb55682.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=22138@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.