From: Leo Famulari <leo@famulari.name>
To: EuAndreh <eu@euandre.org>
Cc: 44821@debbugs.gnu.org
Subject: [bug#44821] [PATCH v2] gnu: Add diff-so-fancy.
Date: Thu, 26 Nov 2020 14:00:42 -0500 [thread overview]
Message-ID: <X7/7WpfrAUEFgItC@jasmine.lan> (raw)
In-Reply-To: <87y2iom9fy.fsf@euandre.org>
On Thu, Nov 26, 2020 at 12:20:17PM -0300, EuAndreh wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > It's impractical to propagate ncurses — ncurses is very widely used and
> > this will cause "profile conflicts" if anyone tries to make a profile
> > that refers to multiple versions of ncurses.
> >
> > Is there any way to make the built package refer explicitly to the
> > ncurses store directory, so that it can be a regular input?
>
> I'm not sure. How could I accomplish that?
>
> I put ncurses as a propagates input because diff-so-fancy relies on it
> for the execution.
>
> Maybe a "(wrap-program ...)" could solve that? I think it would solve
> the problem you raised, right?
Yes, perhaps, or you could substitute the calls to ncurses with the full
store path of the ncurses executable.
next prev parent reply other threads:[~2020-11-26 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 17:14 [bug#44821] [PATCH] gnu: Add diff-so-fancy EuAndreh via Guix-patches via
2020-11-23 18:59 ` [bug#44821] [PATCH v2] " EuAndreh via Guix-patches via
2020-11-25 23:08 ` Leo Famulari
2020-11-26 15:20 ` EuAndreh via Guix-patches via
2020-11-26 19:00 ` Leo Famulari [this message]
2020-11-26 19:44 ` EuAndreh via Guix-patches via
2020-12-03 22:14 ` Ludovic Courtès
2020-12-03 23:16 ` EuAndreh via Guix-patches via
2020-11-23 19:47 ` [bug#44821] [PATCH] " EuAndreh 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=X7/7WpfrAUEFgItC@jasmine.lan \
--to=leo@famulari.name \
--cc=44821@debbugs.gnu.org \
--cc=eu@euandre.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 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).