From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: The case for moving raw binaries
Date: Thu, 28 Apr 2022 18:55:30 +0200 [thread overview]
Message-ID: <65282c9d3d91b215499ab792604e11d0127e5215.camel@telenet.be> (raw)
In-Reply-To: <615054d08116af35720a08a6fdb836e84cf0e873.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Liliana Marie Prikler schreef op do 28-04-2022 om 18:37 [+0200]:
> the shell by typing a dot and using tab completion. What's more, in
> some build systems there might be two (or even more) off them. This
> makes a generic wrap after wrap pattern almost impossible to achieve.
>
> So, what's the fix? I propose moving rawbins to a different location.
> libexec would spring to mind as a place in which we could hide them, so
How does this help with double wrapping? Whether the wrappers /
originals are put in /bin or $RAWBIN_DIR, it's still wrapped twice.
Also, FWIW, double-wrapping works nicely for 'wrap-program' -- it just
appende or prepended some extra X=Y lines. With some work and test
cases, 'wrap-script' could be extended to support such a thing as well.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-28 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 [this message]
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
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=65282c9d3d91b215499ab792604e11d0127e5215.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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).