[Buildroot] perl packages for LTS branch

[Buildroot] perl packages for LTS branch

[Waldemar Brodkorb]

Dear LTS Maintainers,

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/

best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] perl packages for LTS branch

[Thomas Petazzoni via buildroot]

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? 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.

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

Re: [Buildroot] perl packages for LTS branch

[Waldemar Brodkorb]

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

Re: [Buildroot] perl packages for LTS branch

[Thomas Petazzoni via buildroot]

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