aboutsummaryrefslogtreecommitdiffstats
path: root/meta-python/recipes-devtools/python/python3-jinja2_2.11.2.bb
diff options
context:
space:
mode:
authorNarpat Mali <narpat.mali@windriver.com>2023-05-11 16:37:58 +0000
committerArmin Kuster <akuster808@gmail.com>2023-05-16 07:09:25 -0400
commit116bfe8d5e5851e7fc5424f40da8691a19c5b5ee (patch)
treef3def924877727447ee4083e41750c7003e8630a /meta-python/recipes-devtools/python/python3-jinja2_2.11.2.bb
parent4c533a5f902842cd65027c072d2bddd6d7b2b5d3 (diff)
downloadmeta-openembedded-dunfell-next.tar.gz
nodejs: make 14.18.1 available but not defaultdunfell-nextdunfell
Chromium 112 needs nodejs-native version 14 or later. Add the nodejs_14.18.1 recipe from kirkstone: 246b20b92 nodejs: Upgrade to 14.18.1 but, use DEFAULT_PREFERENCE to make sure that the default version of nodejs remains 12.x. 7 patches which were modified between nodejs 12 & nodejs 14 were renamed by adding the suffix "-nodejs14". Note there are some common patches used by nodejs 12 & 14 so, that will require attention during future maintenance. In addition, there were 3 CVE-2022* patches which applied cleanly to nodejs 14 so, they were added to the nodejs 14 recipe. One patch, CVE-llhttp.patch conflicted so, it has not been applied in nodejs 14 yet. Nodejs 14 compile for qemux86-64 but, no run-time testing has been performed. For chromium, we would either require users to modify the local.conf file or we may create a dunfell specific branch in meta-browser. See: https://github.com/OSSystems/meta-browser/pull/709 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Narpat Mali <narpat.mali@windriver.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-jinja2_2.11.2.bb')
0 files changed, 0 insertions, 0 deletions