From: Brendan Tildesley <mail@brendan.scot>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: pratheblackdiamond@gmail.com, 43249@debbugs.gnu.org
Subject: [bug#43249]
Date: Fri, 11 Sep 2020 18:18:21 +1000 [thread overview]
Message-ID: <a8557b34-6258-0ce9-60e5-937d52caf038@brendan.scot> (raw)
In-Reply-To: <87tuw54vhy.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On 10/9/20 11:22 pm, Ricardo Wurmus wrote:
> Brendan Tildesley <mail@brendan.scot> writes:
>
>> I guess then we should patch wrap-program to add
>>
>> (when (wrapper? prog)
>> (error (string-append prog " is a wrapper. Refusing to wrap.")))
> Should it really refuse to wrap or *add* its variables to the existing
> wrapper?
>
If there is a /bin/foo and /bin/.foo-real created by wrap-program, and
we are to run another wrap-program phase, under what circumstances would
it /not/ be a mistake to call (wrap-program "/bin/.foo-real") instead of
(wrap-program "/bin/foo")? And if the first one was called, probably it
was because find-files was used and the packager didn't realise it was
happening, and therefore it will be double-wrapped, like gedit is.
[-- Attachment #2: Type: text/html, Size: 1345 bytes --]
next prev parent reply other threads:[~2020-09-11 8:19 UTC|newest]
Thread overview: 18+ 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
2020-09-07 8:15 ` bug#43151: " Brendan Tildesley
2020-09-08 20:11 ` Andreas Enge
2020-09-09 8:38 ` [bug#43249] " 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 ` [bug#43249] Ricardo Wurmus
2020-09-10 12:46 ` [bug#43249] Brendan Tildesley
2020-09-10 13:22 ` [bug#43249] Ricardo Wurmus
2020-09-11 8:18 ` Brendan Tildesley [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8557b34-6258-0ce9-60e5-937d52caf038@brendan.scot \
--to=mail@brendan.scot \
--cc=43249@debbugs.gnu.org \
--cc=pratheblackdiamond@gmail.com \
--cc=rekado@elephly.net \
/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.