Re: newt:use python3-major instead of python3-majorver

"\"Douglas R. Reno\"" ([email protected] via blfs-dev Mailing List) <[email protected]> Sun, 9 Nov 2025 23:13:34 -0600
Newsgroups gmane.linux.lfs.beyond.devel
Message-ID <CAPBTabL6oRZMSd7_675uPSa93Mh9EunheN-dPqGEkWjZGskC7Q@mail.gmail.com>
On Sun, Nov 9, 2025, 10:58 PM Bruce Dubbs <
[email protected]> wrote:

> On 11/9/25 10:36 PM, Xi Ruoyao ([email protected] via blfs-dev Mailing
> List) wrote:
> > On Mon, 2025-11-10 at 12:30 +0800, Zhang Wen wrote:
> >> Xi Ruoyao <[email protected]> 于2025年11月10日周一 09:54写道:
> >>>
> >>> On Sun, 2025-11-09 at 22:06 +0800, Zhang Wen wrote:
> >>>> On the newt page, we have --with-python=python-3.13 to prevent
> >>>> building the python2 module.
> >>>> This will fail when we have python-3.14 for LFS, so i propose
> >>>> switching to python3-major.
> >>>> This can work even when the python3 version is out of sync, and won't
> >>>> harm anything AFAICS.
> >>>
> >>> The problem is we need to bump the Python version in BLFS or there will
> >>> be too much things not to work.  Being "clever" at one specific case
> >>> won't be really helpful.
> >>>
> >>> Again and again and again that's why we say "Development versions of
> >>> BLFS may not build or run some packages properly if LFS or dependencies
> >>> have been updated since the most recent stable versions of the books."
> >>> for every BLFS package.
> >>>
> >>> --
> >>> Xi Ruoyao <[email protected]>
> >>> --
> >>> http://lists.linuxfromscratch.org/sympa/info/blfs-dev
> >>> Unsubscribe: See the above information page
> >>
> >> In truth i searched for something like 'keep python version in sync
> >> before release' in the tickets and didn't find one.
> >
> > https://wiki.linuxfromscratch.org/blfs/ticket/22244
> >
> >> I searched python3 in the BLFS repo and find that it is only for an
> >> optional dependency of fetchmail for running fetchmailconf.
> >> IMHO, ff we replace this optional dependency with some text
> >> explanation, we can remove python3 from BLFS and things will be more
> >> clear.
> >
> > Even if you drop it from BLFS you still needs a version entity in BLFS.
> > Obviously, you cannot read a version entity from LFS when you render
> > BLFS.  And the version entity is used in a lot of places.
> >
> > $ grep -r 'python3-major' -l | grep -v ^archive | wc -l
> > 93
> >
> > It would be similar to Perl, we still have a Perl version entity in
> > BLFS.
>
>
> Normally the Python version in BLFS would be updated to 3.14 by now, but a
> problem
> with editor availability has put that off.  It should be updated in the
> next week or
> so.  The problem with a new minor version is that all the modules have to
> be rebuilt
> and checked.
>
>    -- Bruce
>
> --
> http://lists.linuxfromscratch.org/sympa/info/blfs-dev
> Unsubscribe: See the above information page


In reply to this and my other tickets I'm working on, I also wanted to
thank everyone for their patience. The past two months have been rough on
me IRL and my time has been a little limited, but that has been getting
much better over the past week or so.

As Bruce said, expect Python to be done any day in the next week.

- Doug

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page