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 15:41:38 -0400 [thread overview]
Message-ID: <20200407194138.GA14915@jasmine.lan> (raw)
In-Reply-To: <224c908df7cf2e32dff2bd31e5050dd4d552093a.camel@zrythm.org>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Tue, Apr 07, 2020 at 08:09:31PM +0100, Alexandros Theodotou wrote:
> Plugins that use the DISTRHO plugin framework (
> https://github.com/DISTRHO/DPF) use the same build/install procedure,
> unless the author makes changes to the Makefiles (like in the case of
> the zam-plugins package). Dragonfly reverb and shiru plugins both use
> DPF as-is, so the build/install procedures are exactly the same - built
> plugins will be produced inside "bin" as binaries, lv2 plugins and vst
> plugins.
>
> There are more DPF-based plugins I plan to package that leave the the
> DPF Makefiles as-is so I thought inheriting from dragonfly-reverb would
> be a nice way to do it.
Okay, feel free to write the packages in whatever way works for you.
> > Does it work to inherit the custom install phase from dragonfly-
> > reverb?
> > It seems like the install-file procedures would not apply here.
However, I tried building it from the patch and the install phase does
fail there.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-07 19:42 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
2020-04-07 19:09 ` Alexandros Theodotou
2020-04-07 19:41 ` Leo Famulari [this message]
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=20200407194138.GA14915@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.