From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.kjellerstedt@axis.com, Ross Burton <Ross.Burton@arm.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Adam X Nilsson <Adam.X.Nilsson@axis.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v1] core-image, populate_sdk_base: Add zsh-completion-pkgs image feature
Date: Tue, 07 Oct 2025 13:41:38 +0100 [thread overview]
Message-ID: <77b7d645b235d4d145afdbea92667357749a7f36.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB5PR02MB102131C9AEB85566B1683DBCBEFE0A@DB5PR02MB10213.eurprd02.prod.outlook.com>
On Tue, 2025-10-07 at 11:48 +0000, Peter Kjellerstedt via lists.openembedded.org wrote:
> > -----Original Message-----
> > From: Ross Burton <Ross.Burton@arm.com>
> > Sent: den 7 oktober 2025 12:34
> > To: Khem Raj <raj.khem@gmail.com>
> > Cc: Adam X Nilsson <Adam.X.Nilsson@axis.com>; openembedded-core@lists.openembedded.org; Adam X Nilsson <Adam.X.Nilsson@axis.com>; Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > Subject: Re: [OE-core] [PATCH v1] core-image, populate_sdk_base: Add zsh-completion-pkgs image feature
> >
> > On 6 Oct 2025, at 22:28, Khem Raj <raj.khem@gmail.com> wrote:
> > >
> > > On Mon, Oct 6, 2025 at 1:10 PM Ross Burton via lists.openembedded.org <ross.burton=arm.com@lists.openembedded.org> wrote:
> > > >
> > > > On 1 Oct 2025, at 17:02, Adam Nilsson via lists.openembedded.org <Adam.X.Nilsson=axis.com@lists.openembedded.org> wrote:
> > > > >
> > > > > From: Adam Nilsson <adamni@axis.com>
> > > > >
> > > > > Add a zsh-completion-pkgs image feature to install *-zsh-completion
> > > > > packages into an image. This is similar to the existing
> > > > > bash-completion-pkgs feature.
> > > >
> > > > By my count there’s just three recipes in core that have -zsh-
> > > > completion packages. Until it’s more common, I’d suggest putting the
> > > > COMPLEMENTARY_GLOBS assignment in your own image recipe if you want to use
> > > > it.
> > >
> > > It does help people using zsh as default shell and working with yocto SDKs.
> >
> > Does it though?
> >
> > $ git grep FILES.*zsh-completion
> > meta/recipes-core/systemd/systemd_257.8.bb:FILES:${PN}-zsh-completion = "${datadir}/zsh/site-functions"
> > meta/recipes-devtools/patchelf/patchelf_0.18.0.bb:FILES:${PN}-zsh-completion = "${datadir}/zsh"
> > meta/recipes-kernel/kmod/kmod_34.2.bb:FILES:${PN}-zsh-completion = "${datadir}/zsh”
> >
> > How many SDKs ship with nativesdk builds of systemd, patchelf, or kmod?
> >
> > Ross
>
> Please think outside OE-Core. Just because there are only three recipes
> in OE-Core that currently create zsh-completion packages, does not mean
> that it is not more common outside of OE-Core. Also, one recipe that
> could benefit from creating a zsh-completion package is bluez5, which
> currently has it disabled.
>
> One of the main reasons I suggested Adam to send this patch upstream
> is for consistency. Since bash-completions-pkgs is a well established
> feature, I would expect the same possibility for others shells (which
> in our case happens to be zsh).
I'm not sure we should have let the bash-completions one in. Now that
we have, we have the inevitable followups and this is why I worry a lot
about precedent when merging patches as people do use it against me
later.
One the one hand, it is a trivial patch. On the other, we have key
features like dev packages and dbg packages being mixed with much lower
priority things like shell completion. This makes it harder for new
users to find the important takeaways from the less important ones.
I really don't know what to do with the patch. I'm not particularly
keen on it and my first impression was no, equally, I'm burnt out and
really don't have the time/energy to write long emails arguing points
about it.
Cheers,
Richard
next prev parent reply other threads:[~2025-10-07 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 16:02 [PATCH v1] core-image, populate_sdk_base: Add zsh-completion-pkgs image feature Adam Nilsson
2025-10-06 20:09 ` [OE-core] " Ross Burton
2025-10-06 21:28 ` Khem Raj
2025-10-07 10:33 ` Ross Burton
2025-10-07 11:48 ` Peter Kjellerstedt
2025-10-07 12:41 ` Richard Purdie [this message]
2025-10-08 20:00 ` Peter Kjellerstedt
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=77b7d645b235d4d145afdbea92667357749a7f36.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Adam.X.Nilsson@axis.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox