All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Date: Sun, 21 Sep 2025 23:43:01 +0200	[thread overview]
Message-ID: <20250921234301.0110130d@foz.lan> (raw)
In-Reply-To: <87qzvza62n.fsf@trenco.lwn.net>

Em Sun, 21 Sep 2025 14:44:48 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@kernel.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

  reply	other threads:[~2025-09-21 21:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 15:05 linux-next: Tree for Sep 19 Mark Brown
2025-09-21  0:17 ` linux-next: Tree for Sep 19 (make htmldocs problem) Randy Dunlap
2025-09-21  8:43   ` Akira Yokosawa
2025-09-21 14:03   ` Jonathan Corbet
2025-09-21 15:59     ` Randy Dunlap
2025-09-21 19:27       ` Jonathan Corbet
2025-09-21 20:32         ` Mauro Carvalho Chehab
2025-09-21 20:44           ` Jonathan Corbet
2025-09-21 21:43             ` Mauro Carvalho Chehab [this message]
2025-09-21 21:56               ` Jonathan Corbet
2025-09-21 22:06                 ` Mauro Carvalho Chehab
2025-09-21 21:10           ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250921234301.0110130d@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.