From: "Yoann Congal" <yoann.congal@smile.fr>
To: <jaipaul.cheernam@est.tech>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [wrynose][PATCH 1/2] perl-cross: add patches for perl-5.42.3
Date: Sat, 14 Nov 2026 01:48:18 +0100 [thread overview]
Message-ID: <DMUIQLAT1QR3.DDFST6CFRWYS@smile.fr> (raw)
In-Reply-To: <20261105170249.55552-1-jaipaul.cheernam@est.tech>
On Thu Nov 5, 2026 at 6:02 PM CET, Jaipaul Cheernam via openembedded-core wrote:
> perl-cross 1.6.4 has no patchset for the 5.42.3 point release and aborts
> configure on unknown versions. Reuse the 5.42.0 patchset, as its
> cnf/diffs/README advises ("Copy the closest available version").
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
> ...rl-cross-add-patches-for-perl-5.42.3.patch | 226 ++++++++++++++++++
> .../perl-cross/perlcross_1.6.4.bb | 1 +
> 2 files changed, 227 insertions(+)
> create mode 100644 meta/recipes-devtools/perl-cross/files/0001-perl-cross-add-patches-for-perl-5.42.3.patch
>
> diff --git a/meta/recipes-devtools/perl-cross/files/0001-perl-cross-add-patches-for-perl-5.42.3.patch b/meta/recipes-devtools/perl-cross/files/0001-perl-cross-add-patches-for-perl-5.42.3.patch
> new file mode 100644
> index 0000000000..a7fbd116f1
> --- /dev/null
> +++ b/meta/recipes-devtools/perl-cross/files/0001-perl-cross-add-patches-for-perl-5.42.3.patch
> @@ -0,0 +1,226 @@
> +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
> +From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> +Date: Thu, 5 Nov 2026 14:00:00 +0000
> +Subject: [PATCH] perl-cross: add patches for perl-5.42.3
> +
> +Reuse the perl 5.42.0 patchset for the 5.42.3 point release.
> +
> +Upstream-Status: Inappropriate [oe-specific; perl-cross goes 5.42.0 -> 5.44.0]
> +Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> +---
> + cnf/diffs/perl5-5.42.3/constant.patch | 1 +
> + cnf/diffs/perl5-5.42.3/dynaloader.patch | 1 +
> + cnf/diffs/perl5-5.42.3/findext.patch | 1 +
> + cnf/diffs/perl5-5.42.3/installscripts.patch | 1 +
> + cnf/diffs/perl5-5.42.3/liblist.patch | 70 +++++++++++++++++++++
> + cnf/diffs/perl5-5.42.3/makemaker.patch | 1 +
> + cnf/diffs/perl5-5.42.3/posix-makefile.patch | 1 +
> + cnf/diffs/perl5-5.42.3/test-checkcase.patch | 1 +
> + cnf/diffs/perl5-5.42.3/test-makemaker.patch | 1 +
> + cnf/diffs/perl5-5.42.3/xconfig.patch | 48 ++++++++++++++
> + 10 files changed, 126 insertions(+)
> + create mode 120000 cnf/diffs/perl5-5.42.3/constant.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/dynaloader.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/findext.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/installscripts.patch
> + create mode 100644 cnf/diffs/perl5-5.42.3/liblist.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/makemaker.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/posix-makefile.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/test-checkcase.patch
> + create mode 120000 cnf/diffs/perl5-5.42.3/test-makemaker.patch
> + create mode 100644 cnf/diffs/perl5-5.42.3/xconfig.patch
Hello,
Shouldn't liblist.patch and xconfig.patch be symlinks to
cnf/diffs/perl5-5.42.0/... ?
I don't know perl-cross very well but it looks to me that the convention
of this directory is "in each version, symlink to an existing file if
present".
Also, it has the nice side effect of making extra clear that you don't
add original code.
If you agree, can you send a v2 with the change?
Thanks!
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-11-14 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 17:02 [wrynose][PATCH 1/2] perl-cross: add patches for perl-5.42.3 Jaipaul Cheernam
2026-11-05 17:02 ` [wrynose][PATCH 2/2] perl: upgrade 5.42.0 -> 5.42.3 Jaipaul Cheernam
2026-11-14 0:48 ` Yoann Congal [this message]
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=DMUIQLAT1QR3.DDFST6CFRWYS@smile.fr \
--to=yoann.congal@smile.fr \
--cc=jaipaul.cheernam@est.tech \
--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