From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>, william.lyu@windriver.com
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] perl: Fix perl-module-* being ignored via COMPLEMENTARY_GLOB
Date: Tue, 23 Jan 2024 10:27:49 +0000 [thread overview]
Message-ID: <efce460b09cdcb14f93751c290c7a38b18b52d3f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-WsY97xBV3cXsORdqGGXOyS9-YqK2w3bac-wzeL_2yJg@mail.gmail.com>
On Tue, 2024-01-23 at 10:35 +0100, Alexander Kanavin wrote:
> On Tue, 23 Jan 2024 at 00:51, Lyu, William via lists.openembedded.org
> <william.lyu=windriver.com@lists.openembedded.org> wrote:
> > > Do you have some examples of these packages which don't exist?
> > >
> > > I'd like to understand why they don't exist and perhaps not have them
> > > listed in PACKAGES in the first place. Creating a load of empty/useless
> > > packages with ALLOW_EMPTY seems a bit pointless/sad.
> >
> > The following is a list of empty packages perl-modules RDEPENDS on.
> >
> > tmp/work/core2-64-poky-linux/perl/5.38.2/packages-split$ find -maxdepth 1 -empty -name 'perl-module-*'
> > ./perl-module-config
> > ./perl-module-warnings-register
> > ./perl-module-vars
> > ./perl-module-strict
> > ./perl-module-config-git
> > ./perl-module-warnings
>
> All of these are special-cased by the recipe to be packaged into the
> main perl package (and it sets RPROVIDES for them too). As the module
> package split is done with do_split_packages(), there are two options:
> - adjust file regexes in calls to that function to exclude the above items
> - (easier, and fine with me) set ALLOW_EMPTY only specifically for the
> above list, and not all module packages.
I have a third option. After calling do_split_packages(), iterate
through RPROVIDES_${PN} and for earch perl-module- item, remove any
matching entry from PACKAGES. Setting PACKAGES is basically what
do_split_packages does so we can tweak it afterwards.
If we remove the items from PACKAGES, the RDEPENDS for perl-modules
will then be correct and we don't have bogus empty packages lying
around.
Cheers,
Richard
next prev parent reply other threads:[~2024-01-23 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 15:49 [PATCH] perl: Fix perl-module-* being ignored via COMPLEMENTARY_GLOB William.Lyu
2024-01-22 19:03 ` [OE-core] " Richard Purdie
2024-01-22 23:51 ` Lyu, William
2024-01-23 9:35 ` Alexander Kanavin
2024-01-23 10:27 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-24 3:22 William.Lyu
2024-01-24 9:44 ` [OE-core] " Alexander Kanavin
2024-01-24 16:26 ` Lyu, William
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=efce460b09cdcb14f93751c290c7a38b18b52d3f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=william.lyu@windriver.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