From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Olivier Dion <olivier.dion@polymtl.ca>, 53324@debbugs.gnu.org
Subject: [bug#53324] [PATCH] gnu: Add uftrace.
Date: Thu, 20 Jan 2022 16:50:07 +0000 [thread overview]
Message-ID: <aca95f882763ba6a9874270f5af37369565b76bf.camel@telenet.be> (raw)
In-Reply-To: <87y23a7b18.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
Ludovic Courtès schreef op do 20-01-2022 om 15:10 [+0100]:
> > If 'ncurses' is used (and depropagated), you probably need to add
> > the
> > search paths of ncurses (TERMINFO_DIRS) to make sure Guix knows to
> > set
> > TERMINFO_DIRS.
>
> IMO we shouldn’t do that: ‘TERMINFO_DIRS’ “belongs” to ncurses, and
> we
> do not add it to each and every program that depends on ncurses.
>
> I understand that not adding ‘TERMINFO_DIRS’ in uftrace can be
> annoying
> due to <https://issues.guix.gnu.org/20255>, but so far consensus has
> been to keep search path specs where they belong.
Did you mean to refer to <https://issues.guix.gnu.org/22138> here
(‘Search paths of dependencies are not honored’)?
We do add SSL_CERT_DIR to guix even though guix it is only used through
guile+openssl (though we seem to forget to add it to many other
packages). We sometimes add XDG_DATA_DIRS and XDG_CONFIG_DIRS to
‘leaf’ packages even though it is (usually) only used by some glib-
related things.
So aside from perhaps 22138, I don't see a problem here. As long as
22138 isn't addressed, how else could Guix determine that some leaf
package needs TERMINFO_DIRS to be set?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-20 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 19:20 [bug#53324] [PATCH] gnu: Add uftrace Olivier Dion via Guix-patches via
2022-01-17 19:34 ` Maxime Devos
2022-01-20 14:10 ` Ludovic Courtès
2022-01-20 16:50 ` Maxime Devos [this message]
2022-01-17 19:39 ` Maxime Devos
2022-01-17 21:02 ` Olivier Dion via Guix-patches via
2022-01-17 21:37 ` Maxime Devos
2022-01-17 21:55 ` Olivier Dion via Guix-patches via
2022-01-18 7:58 ` Maxime Devos
2022-01-17 21:25 ` [bug#53324] [PATCH v2] " Olivier Dion via Guix-patches via
2022-01-20 14:27 ` bug#53324: [PATCH] " Ludovic Courtès
2022-01-20 14:33 ` [bug#53324] " Olivier Dion via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aca95f882763ba6a9874270f5af37369565b76bf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53324@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).