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 F1EDF41FCB; Wed, 30 Aug 2023 11:47:06 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8CBF140279; Wed, 30 Aug 2023 11:47:06 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id D482240277 for ; Wed, 30 Aug 2023 11:47:05 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CFE2E5C00D3; Wed, 30 Aug 2023 05:47:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 30 Aug 2023 05:47:02 -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= 1693388822; x=1693475222; bh=LR6dgbKsRPogaIVnNLE7Ql8hdoRrx3lkYWB 94XV9xDs=; b=Y8o4UEXU5pG1wkVkd7CmznO2FNGFAaT5RwHx3iB+sBGBwRdK/yp YtecdTZizaqgW3253p2+pGohQbhqyvEe6I+6MpFR0Y3MNDpDj2rNgzQRNzD+hhOr +krl5YqfaY8vesbr0NVg5eio9pmd4HrDwh1N834y+85k4B6N15/2tYi8G++Jm92k a0qKyW/YuLEYpKq+W+ROdzABwKWOOVBU9zOijUO5F/76SyYCRYU9YVT8EjK7q4oH YnIet8k7fuZ0gt3MUZywXA4F5zYblsXNL+PmzLCk5JdPPtwqbsPuMDuCFnSXnlhY HvKtfH87oskplEyqZkcZJ8IqACz2gbuYpWw== 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= 1693388822; x=1693475222; bh=LR6dgbKsRPogaIVnNLE7Ql8hdoRrx3lkYWB 94XV9xDs=; b=s/uvZZgrjWdtaTACDxCsfXV7fDd1EpUjLOJeLYom51g8FSt92EH Z7zlgONHMfzYKkk4iZKfiMXLSBuNTnz4tlAAJjrLFBOEqjULk/ZGQSYSg42W+tW0 TCsFO559bik3Y52pbgYZbkwmq9BWDDyd5GsWthdmyFjHQNx7a5/L8vEyan3lmoHB 3UrcEXDURzbVoZubld4fI76COPGrbEk1P07f/AbTKMKrgQCWKzn6nsfcdbrBNYac pIhHVEwtrMM9fG1nnSJfIuCCSr/tIRVAamGMA9BQFgRRWz6sOi+yiw+cTeYsgdml ygFdIr8qENlIndUDpA5uoIYW04bYywDCqsQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudefkedgvddtucetufdoteggodetrfdotf 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 05:47:01 -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 11:47:00 +0200 Message-ID: <4505422.LvFx2qVVIh@thomas> In-Reply-To: References: <20230601153801.118616-1-bruce.richardson@intel.com> <4029524.5fSG56mABF@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 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?