From: iyzsong@member.fsf.org (宋文武)
To: Julien Lepiller <julien@lepiller.eu>
Cc: rekado@elephly.net, 31934@debbugs.gnu.org
Subject: [bug#31934] [PATCH] services: sound: Properly handle alsa-plugins.
Date: Tue, 26 Jun 2018 19:38:44 +0800 [thread overview]
Message-ID: <87o9fxdbgb.fsf@member.fsf.org> (raw)
In-Reply-To: <989ad55f9f17664af266f1f9f5653583@lepiller.eu> (Julien Lepiller's message of "Mon, 25 Jun 2018 17:37:56 +0200")
Julien Lepiller <julien@lepiller.eu> writes:
> Le 2018-06-25 17:34, iyzsong@member.fsf.org a écrit :
>> Oleg Pykhalov <go.wigust@gmail.com> writes:
>>
>>> Hello,
>>>
>>> iyzsong@member.fsf.org (宋文武) writes:
>>>
>>>> Julien Lepiller <julien@lepiller.eu> writes:
>>>
>>> […]
>>>
>>>> Hello, after some hours of searching... I found that we can use the
>>>> 'lib' option in 'pcm_type' and 'ctl_type' to specify the library path
>>>> for alsa plugins, e.g:
>>>
>>> Thats a nice hack :-) Thank you for working on this.
>>>
>>> […]
>>>
>>>> So I think we can make our 'alsa-service' do this, instead of
>>>> patching
>>>> alsa-lib for 'ALSA_PLUGIN_DIR'.
>>>
>>> Done. Here is a patch which I tested on my machine by ‘system
>>> reconfigure’:
>>>
>>
>> Thank you, I modified it to keep the 'pulseaudio? #f' function, and
>> pushed :-)
>
> So maybe we can drop our ALSA_PLUGIN_DIR patch now?
Yes, I think so. @Ricardo, should we do it in core-updates?
next prev parent reply other threads:[~2018-06-26 11:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:39 [bug#31934] [PATCH] Fix ALSA_PLUGIN_DIR usage Julien Lepiller
2018-06-22 19:54 ` Ludovic Courtès
2018-06-22 20:22 ` Julien Lepiller
2018-06-23 21:54 ` Ludovic Courtès
2018-06-24 7:05 ` 宋文武
2018-06-24 10:44 ` [bug#31934] [PATCH] services: sound: Properly handle alsa-plugins Oleg Pykhalov
2018-06-25 15:34 ` bug#31591: " 宋文武
2018-06-25 15:34 ` 宋文武
2018-06-25 15:37 ` Julien Lepiller
2018-06-26 11:38 ` 宋文武 [this message]
2018-06-26 11:49 ` Marius Bakke
2018-06-26 12:34 ` bug#31934: " 宋文武
2018-06-26 12:59 ` [bug#31934] " Marius Bakke
2018-06-26 14:02 ` Ludovic Courtès
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=87o9fxdbgb.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=31934@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=rekado@elephly.net \
/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.