From: Ricardo Wurmus <rekado@elephly.net>
To: Prafulla Giri <pratheblackdiamond@gmail.com>
Cc: 43249@debbugs.gnu.org, mail@brendan.scot
Subject: [bug#43249]
Date: Tue, 08 Sep 2020 21:57:38 +0200 [thread overview]
Message-ID: <87d02wca8d.fsf@elephly.net> (raw)
In-Reply-To: <CAFw+=j1b0cu6mXcdXdVdYkQT7_OswTYVexWCM3iQsvhiWaKSZQ@mail.gmail.com>
Prafulla Giri <pratheblackdiamond@gmail.com> writes:
> I wonder.... perhaps it'd be better altogether if the (wrap-program)
> procedure could be re-written to not make ..*.real.real programs...? That
> would save us a lot of code-duplication...
Looking at the definition of wrap-program in (guix build utils) there is
code that checks if the wrapper already exists; if it does it should
append the new environment variable definitions to the existing
wrapper. It looks like this doesn’t work reliably.
If someone could figure out why that is we could fix this in the next
core-updates cycle.
--
Ricardo
next prev parent reply other threads:[~2020-09-08 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 18:32 [bug#43249] Resolve Calibre run-time dependency Prafulla Giri
2020-09-06 20:09 ` Jonathan Brielmaier
2020-09-07 8:12 ` Brendan Tildesley
[not found] ` <6492c3cc-07e0-b56b-ea72-99d403770755@brendan.scot>
[not found] ` <20200908201144.GA25269@jurong>
2020-09-09 8:38 ` [bug#43249] bug#43151: " Prafulla Giri
2020-09-08 12:22 ` [bug#43249] Prafulla Giri
2020-09-08 13:38 ` [bug#43249] Brendan Tildesley
2020-09-08 19:57 ` Ricardo Wurmus [this message]
2020-09-10 12:46 ` [bug#43249] Brendan Tildesley
2020-09-10 13:22 ` [bug#43249] Ricardo Wurmus
2020-09-11 8:18 ` [bug#43249] Brendan Tildesley
2020-09-11 8:38 ` [bug#43249] Ricardo Wurmus
2020-09-12 11:33 ` [bug#43249] Brendan Tildesley
2020-09-12 12:21 ` [bug#43249] Ricardo Wurmus
2020-09-13 12:43 ` [bug#43249] Brendan Tildesley
2020-09-15 11:50 ` [bug#43249] Prafulla Giri
2020-09-18 13:26 ` [bug#43249] Prafulla Giri
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=87d02wca8d.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=43249@debbugs.gnu.org \
--cc=mail@brendan.scot \
--cc=pratheblackdiamond@gmail.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.
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).