From: Maxime Devos <maximedevos@telenet.be>
To: Nathan Dehnel <ncdehnel@gmail.com>,
55069@debbugs.gnu.org, 51395@debbugs.gnu.org,
49008@debbugs.gnu.org, 49028@debbugs.gnu.org,
46210@debbugs.gnu.org
Subject: [bug#46210] bug#55069: Add some means to find LV2 plugins
Date: Sat, 23 Apr 2022 14:45:54 +0200 [thread overview]
Message-ID: <12b95f88fd08ad5d5ca4ab8ce07eac9a8015501e.camel@telenet.be> (raw)
In-Reply-To: <CAEEhgEs+2WQT=hjbtctXbZZB-Xr7pPesNAettvDPBd2LqL8p0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
> [PATCH] gnu: mda-lv2: Remove unnecessary search-path-specification.
Isn't it currently necessary? Because lv2 doesn't have a LV2_PATH
search path yet.
Nathan Dehnel schreef op vr 22-04-2022 om 17:13 [-0500]:
> It seems DAWs and plugins can't find each other because there is no
> way to find the plugins outside of the store because there is no
> directory where the plugins are aggregated, and $LV2_PATH isn't set.
I think this would be resolved by adding the search path to the 'lv2'
package (and removing it from lv2-mda-piano, mda-lv2 and calf).
> [PATCH] gnu: Add invada-studio-plugins-lv2.
> [PATCH] gnu: Add distrho-ports-lv2.
> [PATCH] gnu: Add omins-lv2.
> [PATCH] Add drumgizmo
The convention is to add the search paths to the users of the plugins,
not the plugins theirselves. Cf. GUILE_LOAD_PATH, LIBRARY_PATH,
MINETEST_MOD_PATH, EMACSLOADPATH, INFOPATH ... See
<https://issues.guix.gnu.org/49533#5>.
The benefit is that this avoids forgetting LV2_PATH for some plugins,
as it only needs to be added to relatively few places (lv2 itself,
maybe guitarix, maybe ir, arour ...).
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-04-23 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 22:13 bug#55069: Add some means to find LV2 plugins Nathan Dehnel
2022-04-23 12:45 ` Maxime Devos [this message]
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=12b95f88fd08ad5d5ca4ab8ce07eac9a8015501e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=46210@debbugs.gnu.org \
--cc=49008@debbugs.gnu.org \
--cc=49028@debbugs.gnu.org \
--cc=51395@debbugs.gnu.org \
--cc=55069@debbugs.gnu.org \
--cc=ncdehnel@gmail.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.