From: "Jonathan GUILLOT" <jonathan@joggee.fr>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v2 0/2] lib/oe/package: fix LOCALE_PATHS scan to create locale packages
Date: Fri, 23 Feb 2024 13:40:39 +0000 [thread overview]
Message-ID: <CZCI1W6673HU.X4JQRJW1T18X@joggee.fr> (raw)
Hi,
The main patch of the series ensures only the subdirectories of paths added to LOCALE_PATHS are scanned to construct the locale packages. Without the check, the CUPS recipe creates packages such as cups-locale-add-class.tmpl because of file /usr/share/cups/templates/add-class.tmpl existence.
New version now also includes a patch for the glibc-locale recipes and its /usr/share/locale/locale.alias file. Until now, the file was added to a package weirdly named glibc-locale-locale.alias package. It was automatically created by the split_locales() function during the do_package step. Now, even if the file is explictly included in a new glic-locale-alias package. Without such a patch, the glibc-locale recipe was also broken by the main LOCALE_PATHS fix.
Regards,
Jonathan GUILLOT
Jonathan GUILLOT (2):
glibc-locale: add an explicit dedicated package for locale.alias file
lib/oe/package: fix LOCALE_PATHS scan to create locale packages
meta/conf/documentation.conf | 2 +-
meta/lib/oe/package.py | 14 +++++++++-----
meta/recipes-core/glibc/glibc-locale.inc | 3 ++-
3 files changed, 12 insertions(+), 7 deletions(-)
base-commit: 4c45f975310184a773b25b8e7d7ef50fba2f7bd6
--
2.43.2
next reply other threads:[~2024-02-23 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 13:40 Jonathan GUILLOT [this message]
2024-02-19 16:19 ` [PATCH v2 2/2] lib/oe/package: fix LOCALE_PATHS scan to create locale packages Jonathan GUILLOT
2024-02-23 9:51 ` [PATCH v2 1/2] glibc-locale: add an explicit dedicated package for locale.alias file Jonathan GUILLOT
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=CZCI1W6673HU.X4JQRJW1T18X@joggee.fr \
--to=jonathan@joggee.fr \
--cc=openembedded-core@lists.openembedded.org \
/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