From: Leo Famulari <leo@famulari.name>
To: Alexandros Theodotou <alex@zrythm.org>
Cc: 40468@debbugs.gnu.org
Subject: [bug#40468] [PATCH 3/3] gnu: Add shiru-lv2.
Date: Tue, 7 Apr 2020 14:25:11 -0400 [thread overview]
Message-ID: <20200407182511.GA9039@jasmine.lan> (raw)
In-Reply-To: <e43d20b120dd66887e587ac9d157dd7d7df4e411.camel@zrythm.org>
On Mon, Apr 06, 2020 at 10:28:35PM +0100, Alexandros Theodotou wrote:
> * gnu/packages/music.scm (shiru-lv2): New variable.
Thanks!
> +(define-public shiru-lv2
> + (let ((commit "08853f99140012234649e67e5647906fda74f6cc")
> + (revision "1"))
> + (package/inherit dragonfly-reverb
If inheriting, we should use the regular inherit procedure, like this:
(package
(inherit dragonfly-reverb)
...)
package/inherit is for special cases related to grafting and replacement
packages. [0]
Anyways, it looks like the inherited fields are build-system,
native-inputs, and arguments. Is the idea that there is some build
complication common to the LV2 plugins that we don't want to copy
around? Maybe we could make a build system for them.
Does it work to inherit the custom install phase from dragonfly-reverb?
It seems like the install-file procedures would not apply here.
What do you think? Sorry if I've missed something.
[0]
https://guix.gnu.org/manual/en/html_node/Security-Updates.html
next prev parent reply other threads:[~2020-04-07 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 14:16 [bug#40468] [PATCH 3/3] gnu: Add shiru-lv2 Alexandros Theodotou
2020-04-06 21:28 ` Alexandros Theodotou
2020-04-07 18:25 ` Leo Famulari [this message]
2020-04-07 19:09 ` Alexandros Theodotou
2020-04-07 19:41 ` Leo Famulari
2020-04-07 20:04 ` Alexandros Theodotou
2020-04-07 20:08 ` Leo Famulari
2020-04-07 20:14 ` Alexandros Theodotou
2020-04-08 15:41 ` Leo Famulari
2020-04-08 15:58 ` Alexandros Theodotou
2020-04-08 16:34 ` Alexandros Theodotou
2020-05-29 1:41 ` bug#40468: " Leo Famulari
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=20200407182511.GA9039@jasmine.lan \
--to=leo@famulari.name \
--cc=40468@debbugs.gnu.org \
--cc=alex@zrythm.org \
/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.