From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 55085184E; Thu, 11 Sep 2025 13:39:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757597950; cv=none; b=sFxVaxM45FTZIVnDsdw3lPwE9ElC1xvP9SCsfP7bfBPSnBACgqBIs9khJEy7Yig4geuvHarnCjwVRPXqBAiG8w3jc4PQpNcWzh3OdHtnBjRa2y7JA2NWYPuH7B0hnjqof4BdN9JhfxqVt9DHu/j5TGhaWod4hDVuSMlWD50JROQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757597950; c=relaxed/simple; bh=BhITpaOyCg0kiAA9rkgScH1CSG96+Xse8zf3imxO7KE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=FWb6Wha7dL4zd6XnP+qSBtFEDVU88NA3fhg0znnr8v/IOjUT7ujG8Hc60NqwDh5BEQUEQGNL0yvt9mvrIyqqob93tpNNjo8u0o7PNhvuy2BfZWpzLLRUD3AaA03DES8nr8VrZkbFFjmUQf+3nE1jgS3EB3cabS/B7MIwqQe4NJk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=h5q8MobS; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="h5q8MobS" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net DB0D940AE3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1757597937; bh=J3SqLsNgJyDKHvN19ZY09r8OGxhHJc/ev7e58fUl1ps=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=h5q8MobSvNmHXvKp4cbNgppohYxwSNVCGTNgObY5s0EOseMCRHBEL6x/CqCl2xnJ3 H9foSNQCofcrslS5Vzb+syEDVAY2JnpfP7eB/kr7i02YNzESiyRSCvz6lTau4U4hDI HzxO5iKlWka4/zmOe5MEZcOTIFU2BNYq1JfcWnZ6sXAnhpTIlaDM+KMknU52LUTAPI AR08dybANkiZrAa9DHKo3xHpVjqn5Yc2mEItkPg/0nqwrh0SgRX3LfjWO9BiTij4rT fT5jKirElurji3iiwAq3Qe/oPBOccIn3IDgKSbwpjMYbA6sPql1fbpUTaHiuHu/QDF Je0LAmD9jnSnA== Received: from localhost (unknown [IPv6:2601:280:4600:2da9::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id DB0D940AE3; Thu, 11 Sep 2025 13:38:56 +0000 (UTC) From: Jonathan Corbet To: Mauro Carvalho Chehab , Jani Nikula Cc: Mauro Carvalho Chehab , Linux Doc Mailing List , =?utf-8?Q?Bj=C3=B6rn?= Roy Baron , Alex Gaynor , Alice Ryhl , Boqun Feng , Gary Guo , Trevor Gross , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org Subject: Re: [PATCH v4 08/19] tools/docs: sphinx-build-wrapper: add a wrapper for sphinx-build In-Reply-To: References: <20250910145926.453f5441@foz.lan> <45888ca6c88071c754784495b4ef69460ea67b4f@intel.com> Date: Thu, 11 Sep 2025 07:38:56 -0600 Message-ID: <87zfb1p0r3.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Mauro Carvalho Chehab writes: > On Thu, Sep 11, 2025 at 01:23:55PM +0300, Jani Nikula wrote: >> > 1. SPHINXDIRS. It needs a lot of magic to work, both before running >> > sphinx-build and after (inside conf.py); >> >> Makes you wonder if that's the right solution to the original >> problem. It was added as a kind of hack, and it stuck. > > The problem is, IMHO, due to the lack of flexibility of sphinx-build: > It should have a way on it to do partial documentation builds. A couple of times I have looked into using intersphinx, making each book into an actually separate book. The thing I always run into is that doing a complete docs build, with working references, would require building everything twice. This is probably worth another attempt one of these years... jon