From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] perl packages for LTS branch
Date: Mon, 26 Oct 2026 22:46:05 +0100 [thread overview]
Message-ID: <at_KHTpsxXu-Vk93@waldemar-brodkorb.de> (raw)
In-Reply-To: <at8LDvBotiu7gDNY@windsurf>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Mon, Oct 26, 2026 at 07:06:33AM +0100, Waldemar Brodkorb wrote:
>
> > I would like to ask if it is possible to add my maintained
> > perl packages from master to LTS branches, namely:
> > package/perl-cgi/
> > package/perl-cgi-session/
> > package/perl-log-message/
> > package/perl-log-message-simple/
> > package/perl-switch/
>
> Hm, why would they do so?
Why not? The packages are really small and does not turn up any build
failures in the autobuilders.
> The point of LTS branches is to maintain
> them in terms of security fixes and bug fixes, with the same
> functional scope as the original release. They are not designed to add
> new features, otherwise it's a dangerous slippery slope with no limit
> to what can/should be backported.
Last time I asked about pam_pkcs11 this was no issue. The LTS
maintainers added it.
I understand it shouldn't be done for complex packages like maybe
Firefox ;), but for so simple packages, why not.
I speak here with my $work hat on, because we maintain the packages
internally and we use LTS. I just want to cleanup the stack of
external packages and patches.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-26 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 6:06 [Buildroot] perl packages for LTS branch Waldemar Brodkorb
2026-10-26 8:12 ` Thomas Petazzoni via buildroot
2026-10-26 21:46 ` Waldemar Brodkorb [this message]
2026-10-27 8:16 ` Thomas Petazzoni via buildroot
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=at_KHTpsxXu-Vk93@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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