Target python recipes are already blacklisted since
https://github.com/shr-project/meta-python2/commit/10c65fc18998d302f34634ffceaf31ab335056dd
so meta-python2 already provides just python-native and necessary
bbclasses (as pythonnative.bbclass and few others).
So I don't want to add another identical python2 recipe in meta-qt5
(which will be included for all meta-qt5 users) while now only a few
recipes in meta-qt5 need meta-python2 layer to be included:
./recipes-qt/qt-kiosk-browser/qt-kiosk-browser_git.bb: if
'meta-python2' not in d.getVar('BBFILE_COLLECTIONS').split():
./recipes-qt/qt-kiosk-browser/qt-kiosk-browser_git.bb: raise
bb.parse.SkipRecipe('qtwebengine dependency requires meta-python2 to
be present.')
./recipes-qt/qt5/qtpdf_git.bb:# still depends on python2
./recipes-qt/qt5/qtpdf_git.bb:# First patch skips "python2" dependency
checks for the pdf module
./recipes-qt/qt5/qtpdf_git.bb:
file://0001-configure.json-remove-python2-dependency.patch \
./recipes-qt/qt5/qtpdf_git.bb:PACKAGECONFIG[webengine-pdf] =
"-feature-webengine-python2,-no-feature-webengine-python2,python3-native"
./recipes-qt/qt5/qtpdf/0001-configure.json-remove-python2-dependency.patch:Subject:
[PATCH] configure.json: remove python2 dependency
./recipes-qt/qt5/qtpdf/0001-configure.json-remove-python2-dependency.patch:-
&& features.webengine-python2
./recipes-qt/qt5/qtwebengine_git.bb:inherit
${@bb.utils.contains("BBFILE_COLLECTIONS", "meta-python2",
"pythonnative", "", d)}
./recipes-qt/qt5/qtwebengine_git.bb: if 'meta-python2' not in
d.getVar('BBFILE_COLLECTIONS').split():
./recipes-qt/qt5/qtwebengine_git.bb: raise
bb.parse.SkipRecipe('Requires meta-python2 to be present.')
./recipes-qt/qt5/qt5-creator_git.bb: if 'meta-python2' not in
d.getVar('BBFILE_COLLECTIONS').split():
./recipes-qt/qt5/qt5-creator_git.bb: raise
bb.parse.SkipRecipe('Requires meta-python2 to be present.')
./recipes-qt/qt5/qtwebview_git.bb: if 'meta-python2' not in
d.getVar('BBFILE_COLLECTIONS').split():
./recipes-qt/qt5/qtwebview_git.bb: raise
bb.parse.SkipRecipe('Requires meta-python2 to be present.')
That's why I've included scarthgap compatibility in my fork of meta-python2.
As there is strong opinion against declaring scarthgap compatibility
in official meta-python2 from Timo, Alex and Jose, I don't plan to
merge Marek's change (nor my version with additional fixes for
Upstream-Status etc).
Maybe usable compromise would be to delete all (already blacklisted)
target recipes from existing meta-python2 and leave only the
python-native to make it even more clear what this layer is
temporarily used for (maybe even with another blacklist by default
like I_REALLY_SWEAR_TO_MIGRATE_TO_PYTHON3_OR_DIE_TRYING) which IMHO
makes better sense than importing this old unsupported python-native
to meta-qt5.
Cheers,
On Tue, Apr 16, 2024 at 4:27 PM Alexander Kanavin
<alex.kana...@gmail.com> wrote:
>
> On Tue, 16 Apr 2024 at 16:19, Peter Marko via lists.openembedded.org
> <peter.marko=siemens....@lists.openembedded.org> wrote:
> > Following works for yocto kirkstone + meta-lts-mixin kirkstone/go +
> > meta-lts-mixin kirkstone/rust + meta-virtualization master
> > LAYERSERIES_COMPAT_virtualization-layer += "kirkstone"
> >
> > meta-qt5 should be able to do something similar with meta-python2 if
> > meta-python2 is frozen...
>
> If I remember right, meta-qt5 does not need target python2, it need
> only native python2 because the qt5 web widget contains a badly
> outdated chromium. So meta-qt5 could just copy the python2 recipe
> directly into the layer perhaps and drop meta-python2 dependency.
>
> Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109982):
https://lists.openembedded.org/g/openembedded-devel/message/109982
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
