Re: newt:use python3-major instead of python3-majorver
"Zhang Wen" ([email protected] via blfs-dev Mailing List) <[email protected]> Mon, 10 Nov 2025 12:30:54 +0800
| Newsgroups | gmane.linux.lfs.beyond.devel |
|---|---|
| Message-ID | <CAKjfnjryZO-ApRZzB-Gbq+f0etegzmxbCEZ-GFxcOYFYre9Oag@mail.gmail.com> |
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. 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. -- Key fingerprint: 419F 72F3 F3A9 36EE 1B72 B00B C1C3 4BD4 FDA3 362F -- http://lists.linuxfromscratch.org/sympa/info/blfs-dev Unsubscribe: See the above information page