unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Olivier Dion <olivier.dion@polymtl.ca>, 53324@debbugs.gnu.org
Subject: [bug#53324] [PATCH] gnu: Add uftrace.
Date: Thu, 20 Jan 2022 15:10:43 +0100	[thread overview]
Message-ID: <87y23a7b18.fsf_-_@gnu.org> (raw)
In-Reply-To: <b1d6000d196517265d05632007a0283f880a5c21.camel@telenet.be> (Maxime Devos's message of "Mon, 17 Jan 2022 20:34:33 +0100")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> Olivier Dion via Guix-patches via schreef op ma 17-01-2022 om 14:20 [-

[...]

>> +      ncurses))
>
> 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.

Thoughts?

Ludo’.




  reply	other threads:[~2022-01-20 20:07 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 [this message]
2022-01-20 16:50     ` Maxime Devos
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=87y23a7b18.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53324@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --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).