[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The case for moving raw binaries
From: |
Liliana Marie Prikler |
Subject: |
Re: The case for moving raw binaries |
Date: |
Mon, 23 May 2022 18:37:47 +0200 |
User-agent: |
Evolution 3.42.1 |
Am Montag, dem 23.05.2022 um 17:10 +0200 schrieb Ludovic Courtès:
> Hi!
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
>
> > "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.
>
> One solution we haven’t yet used to its full potential is ‘wrap-
> script’, an alternative to ‘wrap-program’ that Ricardo added to (guix
> build utils) a while back.
>
> Its advantage is that it does not create a new file. It only works
> for scripts, and only in some languages, but using it more widely may
> already improve the situation noticeably.
Speaking of wrap-script, for Guile in particular wouldn't it make sense
to use sh as a wrap-script wrapper with the #! exec hack?