From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 54392-done@debbugs.gnu.org
Subject: [bug#54392] [PATCH] gnu: cl-3bmd: Update to 4e08d82.
Date: Thu, 17 Mar 2022 10:57:54 -0400 [thread overview]
Message-ID: <20220317105754.GB1986@gac.attlocal.net> (raw)
In-Reply-To: <875yod2bax.fsf@kitej>
On Thu, 17 Mar 2022 09:04:08 +0000 Guillaume Le Vaillant <glv@posteo.net> wrote:
> Patch pushed as a7b40dff2f03b070f848cd30833965541aa9bf7c with some
> modifications.
> By default asdf-build-system reads all the ".asd" files, so you don't
> have to specify the 'asd-files' or 'test-asd-file' parameters, unless
> there is a build failure with the default behavior (e.g. when there is
> a ".asd" file that must not be read, or if they must be read is
> a specific order).
> I also moved sbcl-fiasco fo 'native-inputs' as it is used only for
> testing.
Hi Guillaume,
Thanks for the review and merge and thanks for clarifying that for me
with the asdf-build-system.
PS
I've been trying to package mondo, a nice CL repl. Here's a discussion about
it with fukumachi:
https://github.com/fukamachi/mondo/issues/5
I have a branch here for mondo here:
https://git.sr.ht/~whereiseveryone/guixrus/tree/mondo/item/guixrus/packages/lisp.scm#L1226
I was trying to use the build-program function to produce the CLI executable but
no luck yet.
I'd like to send it to upstream but I'm a bit stuck. Do you happen to know
what I might be missing?
Any help/advice is much appreciated.
all best,
jgart
next prev parent reply other threads:[~2022-03-17 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 21:35 [bug#54392] [PATCH] gnu: cl-3bmd: Update to 4e08d82 jgart via Guix-patches via
2022-03-17 9:04 ` bug#54392: " Guillaume Le Vaillant
2022-03-17 14:57 ` jgart via Guix-patches via [this message]
2022-03-18 9:23 ` [bug#54392] " Guillaume Le Vaillant
2022-03-18 16:02 ` jgart via Guix-patches via
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=20220317105754.GB1986@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=54392-done@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=jgart@dismail.de \
/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.