public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 0/1] sphinx-build-wrapper: add support for skipping sphinx-build
Date: Mon, 22 Sep 2025 20:30:40 +0900	[thread overview]
Message-ID: <f31c2169-cd0e-438a-9e59-d6ebd8eaea6e@gmail.com> (raw)
In-Reply-To: <cover.1758444913.git.mchehab+huawei@kernel.org>

On Sun, 21 Sep 2025 11:13:24 +0200, Mauro Carvalho Chehab wrote:
> Hi Jon,
> 
> This patch adds support for not running sphinx-build at the wrapper
> tool. It was requested by Akira, who wanted to be able to ignore
> Sphinx errors during latex build and still try to build PDF.

Thank you for trying to figure out my intention.
However, you failed to see the point.

> 
> This patch is against docs/build-script and applies after the 3 patch
> series I sent yesterday:
> 
>     https://lore.kernel.org/linux-doc/cover.1758361087.git.mchehab+huawei@kernel.org/
> 
> 
> While Akira's original intention is to have pdfdocs target depend on
> latexdocs, IMO, this is overkill, as probably only Akira and a couple
> of other developers might want to have such behavior.

I think it is only you who don't want such behavior.

> 
> See, after all changes, the makefile rule for *all* doc build targets
> is simple:
> 
>         $(Q)@$(srctree)/tools/docs/sphinx-pre-install --version-check
>         +$(Q)$(PYTHON3) $(BUILD_WRAPPER) $@ \
>                 --sphinxdirs="$(SPHINXDIRS)" $(RUSTDOC) \
>                 --builddir="$(BUILDDIR)" --deny-vf=$(FONTS_CONF_DENY_VF) \
>                 --theme=$(DOCS_THEME) --css=$(DOCS_CSS) --paper=$(PAPER)
> 
> After applying patch 1 from this series, it is really easy to replicate 
> "make -i" by writing a small script that does:
> 
> 	tools/docs/sphinx-pre-install --version-check	
> 	tools/docs/sphinx-build-wrapper latexdocs || echo "LaTeX build failed, but we'll try build PDF anyway"
> 	tools/docs/sphinx-build-wrapper -s pdfdocs
> 

Hello?

You are the one who is changing the way "make pdfdocs" behaves.
All I want is to restore the current behavior, without any need to
use such an ad-hoc script.

Sorry, but I think I have to NAK this.

Furthermore, your "cleanup" is obfuscating the very fact that "pdfdocs"
needs a successful "latexdocs" stage.

I believe Documentation/Makefile is the right place to describe it.

Good luck,
Akira


  parent reply	other threads:[~2025-09-22 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21  9:13 [PATCH 0/1] sphinx-build-wrapper: add support for skipping sphinx-build Mauro Carvalho Chehab
2025-09-21  9:13 ` [PATCH 1/1] tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step Mauro Carvalho Chehab
2025-09-22 11:30 ` Akira Yokosawa [this message]
2025-09-22 12:23   ` [PATCH 0/1] sphinx-build-wrapper: add support for skipping sphinx-build Mauro Carvalho Chehab
2025-09-24  7:03     ` Akira Yokosawa
2025-09-24  9:55       ` 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=f31c2169-cd0e-438a-9e59-d6ebd8eaea6e@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox