From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (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 74DE34204E; Wed, 3 Sep 2025 10:45:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756896339; cv=none; b=GIAkE4yeq9eEmEvoWueMZx2OsxMyNRWVqiKIgLfVEd7oYYDvhdqg3AfHulo7pQDP04cVlZXKxiCiY3oNVVxHp27NjZoAEzukepTIHokpSx2diMp7oLv+2Y+kX4n3TGYhzC+/VghVY+85LBtT+GGvtiMzUK7se+kqG3q4rEBpVz0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756896339; c=relaxed/simple; bh=10p7eDyGz4kyDf+IxN6RpfDdyR829KAOPLqiD+PQ+b8=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=TNYFe/6OT4kfI5593v6fZpO6gtjjuwYymLZhYFinwlL3BmcDkmArl9fED1rZgmaDT8zoNbtallQSzkFrWSsc5E0OuBTtpCEmYQt/OslFSOLHUzXpPSse9FJe4fnIQPhqDf3iYckuG0Sw6h2O9hY3XBKoLz4uViKmG6CB9fVYM8I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=hF29nqav; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="hF29nqav" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=10p7eDyGz4kyDf+IxN6RpfDdyR829KAOPLqiD+PQ+b8=; t=1756896338; x=1758105938; b=hF29nqavFaf0JpIXId9NujDeV0ZCTOb0MHexPjKAFgeIBR7 /0zeSGB/IG8tSiiHjWOoD4OC/9oY9AQxQP3jDEvvb5ONkSM4Hmkue6Hdln4z/0x7jVE+5At17C44n qKtOExICX23ZoTYhl9ODcuFSRIGXhKqvHpR8zToAFY2LaS0s+7kvcw5WRCv0vfv552CDqNnso/yQU sZlWPRffjXhakdCvoGoK0JpoBHLmRQutm/eaTYfWNVH4ydRaPjvZnyvZYAaNKyVB9Nary2hbQrrLO JOeR6ySLvGG2U61oHHwebgHq26+3MNuKQ/NWhfUxC9MSwbjBfl4IWSBlC8jsdjwQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1utkzW-0000000BgzB-0Cva; Wed, 03 Sep 2025 12:45:26 +0200 Message-ID: <431ce4a26d70de6b6d63778e62b732dc035633f9.camel@sipsolutions.net> Subject: Re: [TECH TOPIC] Kernel documentation - update and future directions From: Johannes Berg To: Mauro Carvalho Chehab Cc: Jonathan Corbet , Randy Dunlap , Jani Nikula , Laurent Pinchart , Vegard Nossum , ksummit@lists.linux.dev, Linux Documentation , Akira Yokosawa , Bagas Sanjaya , Matthew Wilcox Date: Wed, 03 Sep 2025 12:45:25 +0200 In-Reply-To: <20250903124229.332dfeae@foz.lan> References: <2f927f53-9af5-4e0c-be8f-f7bdf90e23ff@sirena.org.uk> <20250901204635.51b81ffd@foz.lan> <1bf8a898-e697-46e2-86b1-4158b021d652@sirena.org.uk> <865e583b-4c97-4db1-963c-ed8539fa56dc@sirena.org.uk> <20250902135938.35048fbc@foz.lan> <20250902141434.3e5b14e4@foz.lan> <8339a5dd-446d-4717-9d68-983f5e2354b3@sirena.org.uk> <87ecsox4uy.fsf@trenco.lwn.net> <20250902191929.504977bf@foz.lan> <87frd4vfys.fsf@trenco.lwn.net> <20250903124229.332dfeae@foz.lan> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Wed, 2025-09-03 at 12:42 +0200, Mauro Carvalho Chehab wrote: > > For example, use case we have: using nix-shell to lock down the softwar= e > > used to build, for reproducible builds and similar reasons. Without -- > > pure, PATH may still contain (last!) software from the system itself, > > but it should basically never be used. >=20 > if the PATH is mangled, you'll have a lot more problems than just > building docs as it will pick wrong exec files anyway. Err, no? To search a binary, directories in $PATH are meant to be searched in order of appearance. It's well-defined which one you pick for which, and this setup takes advantage of that (with a rather long $PATH) to control the binaries used for the build. > In the particular case of docs, if you have, for instance, two different > python versions, one with sphinx and another one without it, it may pick > the wrong one, causing the build to fail. There's nothing the build syste= m > can do to solve it. The proper fix would be to wrap the calling logic > to save the env before running under nix-shell, restoring env afterwards. I don't follow. If this setup breaks the build then that's good, I'll fix the env. If the build does magic inside and sort of ignores $PATH, that's bad. johannes