From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] perl packages for LTS branch
Date: Tue, 27 Oct 2026 09:16:40 +0100 [thread overview]
Message-ID: <auBdlYGcrTcDwaPR@windsurf> (raw)
In-Reply-To: <at_KHTpsxXu-Vk93@waldemar-brodkorb.de>
On Mon, Oct 26, 2026 at 10:46:05PM +0100, Waldemar Brodkorb wrote:
> > 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.
I'll leave it up for the LTS maintainers to decide then. For me, LTS
was strictly limited to fixes. Because otherwise it's difficult to
draw the line between what is reasonable to add to LTS ("ho, it's just
a very simple package") and what isn't reasonable ("oh it's a very
simple package, but not completely simple").
Thomas, Titouan, what is your policy?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-27 8:16 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
2026-10-27 8:16 ` Thomas Petazzoni via buildroot [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=auBdlYGcrTcDwaPR@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.