all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: jgart <jgart@dismail.de>, 47815@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#47815] [PATCH 1/3] gnu: music: python-abjad: Abjad Improvements.
Date: Fri, 16 Apr 2021 12:12:25 +0200	[thread overview]
Message-ID: <97a0c2631437f698041b40786a4442e0ff4e5432.camel@telenet.be> (raw)
In-Reply-To: <41ef3171abdaaafbfc405e131de5ab68@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Fri, 2021-04-16 at 04:57 +0000, jgart via Guix-patches via wrote:
> Hi Guix,
> 
> Below are some improvements to the python-abjad package that was merged the other day.
> 
> I changed the name to abjad, moved some inputs into their correct place,

Please move 'lilypond' from propagated-inputs to 'inputs', if sanely possible!
This avoids polluting the profile with packages the user did not
explicitely request.  Of course, abjad still somehow has to find
lilypond, so you might need to replace "lilypond" with

  (string-append (assoc-ref inputs "lilypond") "/bin/lilypond")

somewhere in python-abjad's source code.  You can use substitute*
for that.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-04-16 10: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 [this message]
2021-04-16 17:59   ` jgart via Guix-patches via
2021-04-17  9:12     ` Maxime Devos
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=97a0c2631437f698041b40786a4442e0ff4e5432.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=47815@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --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.