all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via <help-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Pan Xie <xiepan@skyguard.com.cn>
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: Why bash-minimal is part of sbcl package
Date: Tue, 12 Dec 2023 08:51:55 -0800	[thread overview]
Message-ID: <877cljbbys.fsf@lease-up.com> (raw)
In-Reply-To: <87ttonbcns.fsf@gmail.com>

Hi Maxim,

On Tue, Dec 12 2023, Maxim Cournoyer wrote:

> it means bash-minimal should be explicitly added to the inputs,
> otherwise when cross-building the package for another architecture the
> native bash captured wouldn't be executable on the target.

The core-updates branch has a lot of new 'bash-minimal' additions,
presumably for cross-building. Maybe this is a good opportunity to ask
about something I have been working on.

As part of a broader effort to make development in scripting language
like GNU Guile easier, I rewrote the executable wrapper so that it uses
Guile instead of Bash.  My initial hope was that the Guile wrapper could
use /run/current-system/profile/bin/guile (and thereby avoid an explicit
Bash prerequisite) but it is only available on Guix System.

My Guile wrapper will eventually reach you as part of a proposal to
migrate Guix from the Automake build system to my very own Bespoke,
which is likewise written in Guile. Meanwhile, please let me know if
there is any use for a Guile wrapper (instead of Bash). Thanks!

Kind regards
Felix


  reply	other threads:[~2023-12-12 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 10:34 Why bash-minimal is part of sbcl package Pan Xie
2023-12-10  8:58 ` Guillaume Le Vaillant
2023-12-12 16:36 ` Maxim Cournoyer
2023-12-12 16:51   ` Felix Lechner via [this message]
2023-12-12 20:52     ` Maxim Cournoyer

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=877cljbbys.fsf@lease-up.com \
    --to=help-guix@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=xiepan@skyguard.com.cn \
    /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.