From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 518D141FCC; Wed, 30 Aug 2023 13:23:28 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3550A4027F; Wed, 30 Aug 2023 13:23:28 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 5626240277 for ; Wed, 30 Aug 2023 13:23:26 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D99565C00DB; Wed, 30 Aug 2023 07:23:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 30 Aug 2023 07:23:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1693394603; x=1693481003; bh=35kSWoDqgbHU1mXovmfl1W3jK54DZnhiJNa 7p9ojGZE=; b=ShPGUQdXuU1yTEs+EICJW9fknBNCHMtkxcUBXZ1hCNWYm1xPO5g 1QIg/5KOsgqnP/IH1SE+wivzukB7Q+/1Ktw7v4K7HDdaO+GGkIhbVMlgrdFJ5i8O IXLIvlAUqhdkrIHIssdgvAxkdCU32qfe4qsJIVGvyHBZxM/ywufZLG+pwGRBELo9 QPLkULmAzSZ8ldBRmNV+oKhTqsTk8UgWBVPGT+Lm/CtUi5fedQuso2IDVA5Oblxt 18eXLHWlE8ZK54aPDYi6ts50jRJ8DuqY+QfAEYIjBFYR78nOTJmAIH81Td0SI5LB tUKPQonSVO2AY+7rdEsp0D+7Z1JdWIwcILA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693394603; x=1693481003; bh=35kSWoDqgbHU1mXovmfl1W3jK54DZnhiJNa 7p9ojGZE=; b=dP+DiOiwZwupw+LzRG4joGoV8eFN69m2/jGe4visHfpn9OoLd4b 28Wd9/2wKRAv/47Txl2rMOXTN5GQQIGiEa872KYnIfLldNoGl4w8oAWIbSjx0XKh WS++/Or1dPHJsaDafvTZm5DVvypqhP/IqLa041lVr6pbFXpCRYchusU1SNZXHjHZ H4YEyYyZ255Atq5oZzJfJ4TVqB5n5CN5r8OUkhALOX7W7bJS05p0Aept/CSFZ4S/ 5FzbVAVPwQNQ/R5fAShMLitPnx5K+5wspU7R+i7+WK9AULOhNfwuvqs/llXJPwAZ wMtKzXdQHw0wlaQQr2i+VNuvifeZrt5bS9w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudefkedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 30 Aug 2023 07:23:22 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: dev@dpdk.org, David Marchand Subject: Re: [PATCH v3] doc: build manpages as well as html output Date: Wed, 30 Aug 2023 13:23:21 +0200 Message-ID: <4826215.GXAFRqVoOG@thomas> In-Reply-To: References: <20230601153801.118616-1-bruce.richardson@intel.com> <4505422.LvFx2qVVIh@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 30/08/2023 12:20, Bruce Richardson: > On Wed, Aug 30, 2023 at 11:47:00AM +0200, Thomas Monjalon wrote: > > 29/08/2023 12:10, Bruce Richardson: > > > On Tue, Aug 29, 2023 at 11:28:01AM +0200, Thomas Monjalon wrote: > > > > 3/08/2023, Bruce Richardson: > > > > > + meson.add_install_script(mandb) > > > > > > > > When is it executed exactly? Will it update the database in case we > > > > install in a staging directory, when preparing a package for later > > > > deploying on another machine? > > > > > > Yes, it will. Unfortunately, I can't find any way to just call mandb if > > > we are installing in a system manpage location on the local machine. > > > Therefore, I had two options: 1. don't update the manpage database. In > > > this case, the user won't be able to actually get the newly install > > > manpages > > > > The user can update the manpage database himself. And if installing from > > a package, it should have been done automatically. > > > > > 2. always update the local manpage database. In this case, the user > > > installing the docs will find them, but anyone installing to staging > > > will experience a slight delay while their local mandb is updated. > > > > > > I went for #2 on the basis that the delay in the staging case is pretty > > > harmless, while not actually finding the manpages is more serious. > > > > > > However, I'm open to other suggestions on how to work this? > > > > My concern is polluting the machine of the packager. What happens when > > the staging directory is removed? Is it an error when opening a manpage > > later? > > > Running mandb doesn't add the manpages from the staging directory to the > database, it simply triggers a scan of the registered manpage directories > on the system, adding new pages found there. It's the man equivalent of > doing an "ldconfig". Ah OK So there is no more concern, thanks.