From: Peter Korsgaard <peter@korsgaard.com>
To: Charles Hardin <ckhardin@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/alsa-plugins: fix dependencies for the alsa plugin package
Date: Sun, 16 Jul 2023 08:15:36 +0200 [thread overview]
Message-ID: <87zg3wcrg7.fsf@48ers.dk> (raw)
In-Reply-To: <20230620173813.4590-1-ckhardin@gmail.com> (Charles Hardin's message of "Tue, 20 Jun 2023 10:38:12 -0700")
>>>>> "Charles" == Charles Hardin <ckhardin@gmail.com> writes:
> The alsa-utils will remove and create the /usr/share/alsa dir
> as a whole and since the alsa plugins needs to add config into
> this same directory it should come after those install steps.
> Also, the bluez alsa needs the plugins installed to find them
> during the configuration phases - so, interlock the plugins
> when configured.
> Signed-off-by: Charles Hardin <ckhardin@gmail.com>
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-16 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:38 [Buildroot] [PATCH 1/2] package/alsa-plugins: fix dependencies for the alsa plugin package Charles Hardin
2023-06-20 17:38 ` [Buildroot] [PATCH 2/2] package/alsa-plugins: require libsamplerate for the plugins Charles Hardin
2023-06-25 20:04 ` Arnout Vandecappelle via buildroot
2023-07-02 20:17 ` [Buildroot] [PATCH v2 1/1] package/bluez-alsa: allow a samplerate conversion for audio playback Charles Hardin
2023-07-03 19:17 ` Thomas Petazzoni via buildroot
2023-06-25 19:57 ` [Buildroot] [PATCH 1/2] package/alsa-plugins: fix dependencies for the alsa plugin package Arnout Vandecappelle via buildroot
2023-07-16 6:15 ` Peter Korsgaard [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=87zg3wcrg7.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ckhardin@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.
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.