[tlbuild] running TL24 pretest on OpenBSD

[luigi scarso]

On Wed, 21 Feb 2024 at 06:46, Norbert Preining <norbert at preining.info> wrote:
>
> Hi Karl, hi Robert!
>
> On Tue, 20 Feb 2024, Karl Berry wrote:
> > Hi Robert!
> >
> >     running eg. x.y at the time when x.(y+2)
> >     has been released is fine, and I know quite a
> >     number of people who are doing this.
> >
> > I didn't know that. That seemingly makes it sensible for us to include
> > openbsd binaries in our upstream TL, for the benefit of such
>
> I agree with that.
>
> >     the binaries with the version number in the name ("openbsd7.4"
> >
> > Good thought.
>
> I also think that this would be better in principle, but it creates a few problems with
> updates, though:
>         TL2024  openbsd7.4
>         TL2025  openbsd7.6
> are different archs, so updating in place will not work out of the box.
>
> So I am somehow torn what would be better.
>
>
> > Makes me think maybe the better answer is to link to binary sets on
> > https://tug.org/texlive/custom-bin.html and let users do it that way,
> > instead of incorporating them in TL directly. --thanks, karl.
>
> It feels a bit second-class citizen, though.


Following
https://www.openbsd.org/faq/faq5.html
"""
There are three flavors of OpenBSD:
releases: The version of OpenBSD shipped every six months.
-current: The development branch. Every six months, -current is tagged
and becomes the next release.
-stable: A release plus patches found on the errata page. When very
important fixes are made to -current, they are backported to the
supported -stable branches.
Only the two most recent OpenBSD releases receive security and
reliability fixes for the base system.
New users should be running either -stable or a release. That being
said, many people do run -current on production systems to help catch
bugs and test new features.
"""

to be consistent with the openbsd approach to the security  each year
we should have 2 openbsd releases (latest and latest-1) e.g.
         TL2024  openbsd7.4
         TL2024  openbsd7.5

It's a complex task in my opinion
(from my pov of luatex maintainer this means that I have to be in sync
with the openbsd activity in TL),   as it has to be if security is on
the top of the list.

Perhaps
TL<X> openbsd-current
is easier to manage and better than nothing.

--
luigi