From: Maxime Devos <maximedevos@telenet.be>
To: jgart <jgart@dismail.de>, 47815@debbugs.gnu.org
Cc: "Bonface Munyoki K." <me@bonfacemunyoki.com>,
Efraim Flashner <efraim@flashner.co.il>,
"Bonface M. K." <bonfacemunyoki@gmail.com>
Subject: [bug#47815] [PATCH 1/3] gnu: music: python-abjad: Abjad Improvements.
Date: Sat, 17 Apr 2021 11:12:25 +0200 [thread overview]
Message-ID: <9d82233085aadf8a622f2956e5fc8c51a134c7ca.camel@telenet.be> (raw)
In-Reply-To: <baed24528899846a824662f850a68427@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
jgart schreef op vr 16-04-2021 om 17:59 [+0000]:
> Hi Maxime,
>
> Thank you for the review! I attached a new patch set.
>
> I reverted to Bonface's original idea of having lilypond only as a native input
> in the package definition.
If you do that, make sure "abjad" does not retain a reference to lilypond,
as otherwise when cross-compiling, "abjad" will use a lilypond built for the
incorrect architecture. You can use #:disallowed-references ,lilypond for this.
(TODO: there should be a #:disallowed-refences/native variant. But
#:disallowed-references will suffice for now.)
I'm currently occupied with some other things, so I can't review your revised
patches yet.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-04-17 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7988a3c09cc5efb9265b28483f036b1508514f67.camel@telenet.be>
2021-04-16 4:57 ` [bug#47815] [PATCH 1/3] gnu: music: python-abjad: Abjad Improvements jgart via Guix-patches via
2021-04-16 10:12 ` Maxime Devos
2021-04-16 17:59 ` jgart via Guix-patches via
2021-04-17 9:12 ` Maxime Devos [this message]
2021-04-17 16:10 ` jgart via Guix-patches via
2021-07-22 8:53 ` bug#47815: " Efraim Flashner
2021-04-17 16:19 ` [bug#47815] Fwd: Re: [bug#47815] " Maxime Devos
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=9d82233085aadf8a622f2956e5fc8c51a134c7ca.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=47815@debbugs.gnu.org \
--cc=bonfacemunyoki@gmail.com \
--cc=efraim@flashner.co.il \
--cc=jgart@dismail.de \
--cc=me@bonfacemunyoki.com \
/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.