All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 4/5] alsa-utils: dynamically split the packages instead of doing it manually
Date: Thu, 08 Jan 2026 16:02:24 +0100	[thread overview]
Message-ID: <DFJARNRE99CT.174ED819MH46Y@bootlin.com> (raw)
In-Reply-To: <20260107153803.2905889-4-ross.burton@arm.com>

On Wed Jan 7, 2026 at 4:38 PM CET, Ross Burton via lists.openembedded.org wrote:
> Instead of hard-coding a long list of packages and the FILES, we can
> use do_split_packages to do the bulk of the work for us.
>
> Leave the SUMMARY (and add some which were missing) and the FILES that
> are needed to catch extra files for each package.
>
> This removes the alsa-utils-scripts package which only existed to isolate
> the bash depedencies, and instead adds separate -alsaconf and -alsa-info
> packages for each of the scripts.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---

Hi Ross,

This one has a lot of conflicts with the alsa update to 1.2.15.1. As
this update is now merged, can I ask you to rebase this series onto
master?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-01-08 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 15:37 [PATCH 1/5] alsa-utils: build more manpages with rst2man Ross Burton
2026-01-07 15:38 ` [PATCH 2/5] alsa-utils: no need to install scripts manually Ross Burton
2026-01-07 15:38 ` [PATCH 3/5] alsa-utils: clean up udev PACKAGECONFIG Ross Burton
2026-01-07 15:38 ` [PATCH 4/5] alsa-utils: dynamically split the packages instead of doing it manually Ross Burton
2026-01-08 15:02   ` Mathieu Dubois-Briand [this message]
2026-01-07 15:38 ` [PATCH 5/5] pulseaudio: depend on alsa-utils-alsa-info as that is the new package name Ross Burton

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=DFJARNRE99CT.174ED819MH46Y@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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.