From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/perl: bump to version 5.34.0
Date: Tue, 20 Dec 2022 17:24:10 +0100 [thread overview]
Message-ID: <20221220162410.GI2909@scaer> (raw)
In-Reply-To: <20220102104318.2631-1-francois.perrad@gadz.org>
François, All,
On 2022-01-02 11:43 +0100, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
[--SNIP--]
> diff --git a/package/perl/perl.mk b/package/perl/perl.mk
> index f661fef01..d7f9c58dd 100644
> --- a/package/perl/perl.mk
> +++ b/package/perl/perl.mk
> @@ -5,8 +5,8 @@
> ################################################################################
>
> # When updating the version here, also update utils/scancpan
You forgot to also update utils/scancpan, as the comment above, also
authored by you, instructs. ;-)
So I've pushed a fix-up commit to master.
Ideally, there should be an auto-detection in place, so that we do not
have to manually sync the two. Could you have a look into that, please?
Regards,
Yann E. MORIN.
> -PERL_VERSION_MAJOR = 32
> -PERL_VERSION = 5.$(PERL_VERSION_MAJOR).1
> +PERL_VERSION_MAJOR = 34
> +PERL_VERSION = 5.$(PERL_VERSION_MAJOR).0
> PERL_SITE = https://www.cpan.org/src/5.0
> PERL_SOURCE = perl-$(PERL_VERSION).tar.xz
> PERL_LICENSE = Artistic or GPL-1.0+
> @@ -15,7 +15,7 @@ PERL_CPE_ID_VENDOR = perl
> PERL_DEPENDENCIES = $(TARGET_NLS_DEPENDENCIES)
> PERL_INSTALL_STAGING = YES
>
> -PERL_CROSS_VERSION = 1.3.5
> +PERL_CROSS_VERSION = 1.3.6
> # DO NOT refactor with the github helper (the result is not the same)
> PERL_CROSS_SITE = https://github.com/arsv/perl-cross/releases/download/$(PERL_CROSS_VERSION)
> PERL_CROSS_SOURCE = perl-cross-$(PERL_CROSS_VERSION).tar.gz
> --
> 2.32.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-12-20 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 10:43 [Buildroot] [PATCH] package/perl: bump to version 5.34.0 Francois Perrad
2022-01-04 17:57 ` Arnout Vandecappelle
2022-12-20 16:24 ` Yann E. MORIN [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=20221220162410.GI2909@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.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