From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Philip McGrath <philip@philipmcgrath.com>,
Maxime Devos <maximedevos@telenet.be>,
guix-devel@gnu.org
Subject: Re: The case for moving raw binaries
Date: Thu, 04 Aug 2022 18:53:58 +0200 [thread overview]
Message-ID: <6f0f00cfa9f95af8f226c508c2074792bbbf5c89.camel@gmail.com> (raw)
In-Reply-To: <87czdgpewg.fsf@gnu.org>
Am Donnerstag, dem 04.08.2022 um 10:54 +0200 schrieb Ludovic Courtès:
> Hi,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
>
> > 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.
>
> That’s already happening:
>
> --8<---------------cut here---------------start------------->8---
> $ head -3 < $(guix build reuse)/bin/reuse | tail -1
> exec -a "$0" "/gnu/store/iwsddc43xqxz4ibncrd7cgv4qjdy0jjd-reuse-
> 1.0.0/bin/.reuse-real" "$@"
> --8<---------------cut here---------------end--------------->8---
>
> I’m not sure why it doesn’t have the desired effect though.
I found out: it's because reuse is a python script and the exec -a hack
stops working because python initializes sys.args using the filename.
Cheers
next prev parent reply other threads:[~2022-08-04 16:55 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
2022-08-04 8:54 ` Ludovic Courtès
2022-08-04 16:53 ` Liliana Marie Prikler [this message]
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=6f0f00cfa9f95af8f226c508c2074792bbbf5c89.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).