From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: guix-devel@gnu.org
Subject: The case for moving raw binaries
Date: Thu, 28 Apr 2022 18:37:11 +0200 [thread overview]
Message-ID: <615054d08116af35720a08a6fdb836e84cf0e873.camel@gmail.com> (raw)
Hi Guix,
"raw binaries" (henceforth rawbins) are the unwrapped binaries that
Guix leaves behind in $PACKAGE/bin with the .$WRAPPER-real name. This
practise causes several issues. For one, those rawbins are visible in
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
would a new directory in the root of $PACKAGE. Other than that, adding
a rawbin output would also be possible, but I am not certain whether
that'd be the right tradeoff.
So, what do you think? Any candidates for $RAWBIN_DIR that we can
bikeshed? Any disagreements?
Cheers
next reply other threads:[~2022-04-28 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 16:37 Liliana Marie Prikler [this message]
2022-04-28 16:50 ` The case for moving raw binaries 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=615054d08116af35720a08a6fdb836e84cf0e873.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
/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.