[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250921234301.0110130d@foz.lan>
Date: Sun, 21 Sep 2025 23:43:01 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>, Mark Brown <broonie@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing
List <linux-kernel@...r.kernel.org>, "open list:DOCUMENTATION"
<linux-doc@...r.kernel.org>, Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Em Sun, 21 Sep 2025 14:44:48 -0600
Jonathan Corbet <corbet@....net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>
> > do you know what is this "alts" file? Is it a custom script or
> > binary?
>
> It's the alternatives mechanism that openSUSE uses.
See my RFC patch. It fixes the issue when PYTHON3 is not explicitly set.
> I have no idea why
> they felt the need to employ it for Sphinx, but they did, so we need to
> work with that kind of configuration. Meaning, really, I think we have
> to just invoke sphinx-build directly rather than trying to control which
> version of Python it may ultimately get.
True, but if we ignore PYTHON3 env completely, this will break on
other setups where sphinx is installed with a different python version
(with includes OpenSUSE non-thumbleweed).
Thanks,
Mauro
Powered by blists - more mailing lists