From: Brendan Tildesley <mail@brendan.scot>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 43249@debbugs.gnu.org
Subject: [bug#43249]
Date: Sat, 12 Sep 2020 21:33:57 +1000 [thread overview]
Message-ID: <00cb09fe-a5bb-2713-6683-bbda733f4839@brendan.scot> (raw)
In-Reply-To: <87een83dy8.fsf@elephly.net>
On 11/9/20 6:38 pm, Ricardo Wurmus wrote:
> Brendan Tildesley <mail@brendan.scot> writes:
>
>> 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.
> Oh, yes, that would be a mistake.
>
While we're at it, what do you think about changing the moved file from
/bin/.foo-real into /bin/.real/foo, or maybe it would have to go up a
directory and go into /.bin-real/foo. That would mean all these dot
files wouldn't pollute PATH and appear in things like bemenu, or in
window titles. Also pkill should be able to kill correctly based on the
name. Would it break more things somehow?
next prev parent reply other threads:[~2020-09-12 11:35 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 ` [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 ` [bug#43249] Brendan Tildesley
2020-09-11 8:38 ` [bug#43249] Ricardo Wurmus
2020-09-12 11:33 ` Brendan Tildesley [this message]
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=00cb09fe-a5bb-2713-6683-bbda733f4839@brendan.scot \
--to=mail@brendan.scot \
--cc=43249@debbugs.gnu.org \
--cc=ludo@gnu.org \
--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 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).