From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Philip McGrath <philip@philipmcgrath.com>,
Maxime Devos <maximedevos@telenet.be>,
guix-devel@gnu.org
Subject: Re: The case for moving raw binaries
Date: Sat, 30 Jul 2022 08:11:22 +0200 [thread overview]
Message-ID: <13b8c0fc0e22400a0b455a828f31166c4986b132.camel@gmail.com> (raw)
In-Reply-To: <21016dde-9075-43b2-a539-e72967f55603@www.fastmail.com>
Am Freitag, dem 29.07.2022 um 17:20 -0400 schrieb Philip McGrath:
> Hi,
>
> [...]
> I was mildly annoyed recently with several programs that use the
> ".foo-real" name in their `--help` output, for example:
>
> ```
> $ guix shell --pure reuse -- reuse -h
> usage: .reuse-real [-h] [--debug] [--include-submodules]
> ```
>
> I wondered about just changing `wrap-program` to put the real program
> at `.real/foo` instead of `.foo-real`. One advantage is that it
> wouldn't need any special cooperation like setting up an output or an
> environment variable.
Even as the one who made the suggestion that issue has an easier
workaround: Use exec -a to pass the 0th argument unchanged.
Cheers
next prev parent reply other threads:[~2022-07-30 6:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 16:37 The case for moving raw binaries Liliana Marie Prikler
2022-04-28 16:50 ` Maxime Devos
2022-04-28 16:55 ` Maxime Devos
2022-04-28 17:27 ` Liliana Marie Prikler
2022-04-28 19:57 ` Maxime Devos
2022-04-28 22:52 ` raingloom
2022-04-29 9:39 ` Maxime Devos
2022-04-29 4:13 ` Liliana Marie Prikler
2022-04-29 9:27 ` Maxime Devos
2022-04-29 16:59 ` Liliana Marie Prikler
2022-07-29 21:20 ` Philip McGrath
2022-07-30 6:11 ` Liliana Marie Prikler [this message]
2022-08-04 8:54 ` Ludovic Courtès
2022-08-04 16:53 ` Liliana Marie Prikler
2022-04-29 9:18 ` zimoun
2022-05-23 15:10 ` Ludovic Courtès
2022-05-23 16:03 ` Maxime Devos
2022-05-23 16:37 ` Liliana Marie Prikler
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=13b8c0fc0e22400a0b455a828f31166c4986b132.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=philip@philipmcgrath.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).