From: Sughosha via Guix-patches via <guix-patches@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 64113@debbugs.gnu.org
Subject: [bug#64113] [PATCH] gnu: Add missing native search paths to audio plugins.
Date: Wed, 01 Nov 2023 06:23:55 +0000 [thread overview]
Message-ID: <DFlp2P8-A0EH7AezY30hntKl-23R8YK8IfgdME5ndAG7U3OHIBNR0n7XQ10v-t3fubBWVzfFwLA_iPq8hM2zUeXkHVi3WxuASYBjo6xN3N4=@proton.me> (raw)
In-Reply-To: <87wmx8whdu.fsf@gmail.com>
Hi Maxim,
------- Original Message -------
Maxim Cournoyer <maxim.cournoyer@gmail.com> schrieb am Samstag, 2. September 2023 um 20:37:
> You seem to be adding these search paths to plugins, which is
> unexpected from my understanding: a plugins by itself does nothing; the
> search paths should rather be defined on the consumer of the plugins
> (e.g. Ardour), no?
>
> --
> Thanks,
> Maxim
Oh yes. I think what you are saying is right. The search path should rather be defined on the consumer of the plugins, like Ardour and Qtractor. I read in this article, <https://guix.gnu.org/blog/2019/guix-profiles-in-practice/>, which asks to add man-db, info-reader or pkg-config to the profile manifest, so adding search path to every package with man pages does not make any sense. I think this issue can be closed now.
Thanks,
Sughosha.
next prev parent reply other threads:[~2023-11-01 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:07 [bug#64113] [PATCH] gnu: Add missing native search paths to audio plugins Sughosha via Guix-patches via
2023-09-02 18:37 ` Maxim Cournoyer
2023-11-01 6:23 ` Sughosha via Guix-patches via [this message]
2023-11-01 19:28 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='DFlp2P8-A0EH7AezY30hntKl-23R8YK8IfgdME5ndAG7U3OHIBNR0n7XQ10v-t3fubBWVzfFwLA_iPq8hM2zUeXkHVi3WxuASYBjo6xN3N4=@proton.me' \
--to=guix-patches@gnu.org \
--cc=64113@debbugs.gnu.org \
--cc=Sughosha@proton.me \
--cc=maxim.cournoyer@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).