From: Maxime Devos <maximedevos@telenet.be>
To: raingloom <raingloom@riseup.net>
Cc: guix-devel@gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: Re: The case for moving raw binaries
Date: Fri, 29 Apr 2022 11:39:09 +0200 [thread overview]
Message-ID: <c93cdf6e9397e0a7cccde503d7335da8c7277c54.camel@telenet.be> (raw)
In-Reply-To: <20220429005247.4af8b0a4@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
raingloom schreef op vr 29-04-2022 om 00:52 [+0200]:
> It should be pretty easy to detect a wrapped binary without moving it.
> We could just include a magic string in it and scan for that, the exact
> same way we scan for store references. If it contains the "wrapped"
> magic UUID, it's wrapped.
This is already the case, at least for 'wrap-program':
(define (wrapped-program? prog)
"Return #t if PROG is a program that was moved and wrapped by 'wrap-
program'."
[...])
[...]
(when (wrapped-program? prog)
(error (string-append prog " is a wrapper. Refusing to wrap.")))
(if already-wrapped?
;; PROG is already a wrapper: add the new "export VAR=VALUE"
lines just
;; before the last line.
[...])
[...]
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-29 10:15 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 [this message]
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=c93cdf6e9397e0a7cccde503d7335da8c7277c54.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=raingloom@riseup.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).