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 6F390A0C3F for ; Sat, 12 Jun 2021 01:14:38 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6952C4003F; Sat, 12 Jun 2021 01:14:38 +0200 (CEST) Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2064.outbound.protection.outlook.com [40.107.237.64]) by mails.dpdk.org (Postfix) with ESMTP id 19718406A2 for ; Sat, 12 Jun 2021 01:14:37 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Rd2lufmtStu4yGlSFr1JoJuRfNTaQJzW2ciN8l+eUV2RvUsPJDOYXtxjU8iE4PwNmf8AWLTQzBRojdkrxymj0FjQbiwhsG3Our6xLNad0XbKsXWuI0BLlYgeaEguI5JMTo+T5QRgXeaegIYiBYFZ2Dlx10CcjgV3ceeseg5kA3TJQhfTQgU3HOI9ICozOnAy0Ahr46WwpWTiUt/9zUvJeqj4hKukej4brtBCfQBt0sWZCcR1LqujZhG2I0ZdhZ+lEdDnpE0ZOqC5zCtSHWFvtygSTiBnK/dtjAgQgDsVFrsM6IzMszrNIMwC8BgWwVvvT2ce24/HvVDCxImIcgXNEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JAhmqu/T1cBVgVlkDo91iIbbHXRGLy2BjLuSmAR3MIg=; b=NZwRhJWsbxMEgu7XQoyNmvKmXlMfgI9sEZ+Wi6+7WuSf3o4sRPvpYzmGt/0bIroWFyS7KnrYK9VVs2m2yQMHu8NXjwM33RhdnKDirjx9pxKM826DVj/CqY08gHiLdTFEnkJrq3juCeJXmC9A9/tQj6xYA2PCC+6NvqGLGRT9GcUWclJlWKCGnZla/lbbhFeQPqaCwhIelFWA7H0HQLPed7eTJdsG/j5b5PXzwJQ53810zY+KHwiexdm7kC1uggOIjvgbjpDeX8Asgcd0u8XBVKzrm9vZ6CXC8OzUByJ3642gT+kgc4Pf/MbexJrcs7zBmmKCt9o9PGuYMnUxsAqfmQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 216.228.112.34) smtp.rcpttodomain=arm.com smtp.mailfrom=nvidia.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=nvidia.com; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Nvidia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JAhmqu/T1cBVgVlkDo91iIbbHXRGLy2BjLuSmAR3MIg=; b=Ugi/g31odc/DB1ZyaQeWkvwgLDELecseHDA/bml9XIutle3NoaddyJwvS6uyHggOAO2feT7KMyqRuvQuuSW2RkvlIW6oyX/krpikNu1nAhBUFpRJRoXMSHT16sy7yl4wIp9rUfO/WaUwdSG2IZf/tXlJnzfjyQ0r2JwWUNqSP8x6F3B1zMlzjJ7H/77S+b8QoRZocZ+rrMdo4sHcytxQhaiJJgVykdX4TRj3LmsC95PKoS7egHXvMOGG1b0NLC7SkEEKIIIGl02CANNzCpdaBjx0OEkaExD3tBn0fxv2+WZNG88S5qm5TCj+1t80Tks3J6+S9mVCFG2dWrpMnsze0w== Received: from BN8PR04CA0024.namprd04.prod.outlook.com (2603:10b6:408:70::37) by MWHPR12MB1567.namprd12.prod.outlook.com (2603:10b6:301:d::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.20; Fri, 11 Jun 2021 23:14:31 +0000 Received: from BN8NAM11FT014.eop-nam11.prod.protection.outlook.com (2603:10b6:408:70:cafe::c4) by BN8PR04CA0024.outlook.office365.com (2603:10b6:408:70::37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.21 via Frontend Transport; Fri, 11 Jun 2021 23:14:31 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 216.228.112.34) smtp.mailfrom=nvidia.com; arm.com; dkim=none (message not signed) header.d=none;arm.com; dmarc=pass action=none header.from=nvidia.com; Received-SPF: Pass (protection.outlook.com: domain of nvidia.com designates 216.228.112.34 as permitted sender) receiver=protection.outlook.com; client-ip=216.228.112.34; helo=mail.nvidia.com; Received: from mail.nvidia.com (216.228.112.34) by BN8NAM11FT014.mail.protection.outlook.com (10.13.177.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.4219.21 via Frontend Transport; Fri, 11 Jun 2021 23:14:30 +0000 Received: from nvidia.com (172.20.187.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 11 Jun 2021 23:14:28 +0000 From: Xueming Li To: Thomas Monjalon CC: Luca Boccassi , Ruifeng Wang , dpdk stable Date: Sat, 12 Jun 2021 07:03:16 +0800 Message-ID: <20210611230433.8208-102-xuemingl@nvidia.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210611230433.8208-1-xuemingl@nvidia.com> References: <20210510160258.30982-229-xuemingl@nvidia.com> <20210611230433.8208-1-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [172.20.187.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 4c43f52b-c405-46fb-61c3-08d92d2eab16 X-MS-TrafficTypeDiagnostic: MWHPR12MB1567: X-LD-Processed: 43083d15-7273-40c1-b7db-39efd9ccc17a,ExtAddr X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: 2N+gKKPD/DPp1KSbo5mcVWjB+VO3ZCYbgef3CIEne69r7Yaas1yk3sNUEvvp6b29vvmGyls0h0pqaJbSZg6V4Mgsi/sofXoCjzrFYrHdjUdlZSGwz+0XIZfhg3jF8hvq7iP1FcaNKjOg1nwKVAyrtl+YXXmqWctY7d52hwTbB8FUEghtN677GUpID1DyaUo6z2cIkLSDnC7fisVcefwV2SS2J45T/rhaRRF20tQ44v4QnkXfKjl1REWrUqaBiu4NXqDng/kd2WLMaRi5t2muL0Px5V8iqC6ofYpJQx8LJ4V0jPsdBrjei0pIUUvXNVNLh013nZr+6fCf8fCeWUhFyE4AQ1a0MIOhIr77ecaB7sa15yHdtB8gmUoRnElYTKPn+R7M1I+JaPNv/F+Pv2GtZ2BQFhfeWLkOYVdFmVIdOkkv2lh1O5Rwe9TMMf7ZOnywjSYQfl4k2o237DwNNh0S45oFlvlMCDiQps2EqIfSlHb+QbOeyZ8DiarxOEX4ugrTipJ6IXrVDj3Aal/XhgK1RXxpIu5p1SNV0+lyOUOGPPBrvXkJ5uu1+Uz8jbvxscbUbAtsLcCI7sBr2VWXAEA7Tlqe8o9W5czbROg+5m3DSCRhea0pSOlTrkVimDNeGjJ2tENfZ5pLLO9XP9aHlzsmQCdO+kZmOkiGfB8zhy4rR+SfCUWKzsrwn8O6ySugPYDIcbr2RLSQ/aslmYhTzuEN5M4vtXqkJI4smPRb6E7uBuF6QO5/zSgvtcrYFXwrBMOjVygQaGDnjIpD9ADqSvg+2km7RQoYkO35a8qMi6u5fQnWLjgGyCtMUK/mHP5EjMSQ X-Forefront-Antispam-Report: CIP:216.228.112.34; CTRY:US; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:mail.nvidia.com; PTR:schybrid03.nvidia.com; CAT:NONE; SFS:(4636009)(396003)(346002)(376002)(136003)(39860400002)(46966006)(36840700001)(16526019)(36756003)(30864003)(55016002)(8676002)(478600001)(356005)(336012)(5660300002)(2616005)(83380400001)(70586007)(426003)(966005)(82310400003)(70206006)(2906002)(186003)(26005)(1076003)(4326008)(53546011)(54906003)(47076005)(6286002)(6916009)(36860700001)(6666004)(86362001)(82740400003)(316002)(7696005)(36906005)(7636003)(8936002); DIR:OUT; SFP:1101; X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2021 23:14:30.9363 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 4c43f52b-c405-46fb-61c3-08d92d2eab16 X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=43083d15-7273-40c1-b7db-39efd9ccc17a; Ip=[216.228.112.34]; Helo=[mail.nvidia.com] X-MS-Exchange-CrossTenant-AuthSource: BN8NAM11FT014.eop-nam11.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR12MB1567 Subject: [dpdk-stable] patch 'doc: remove PDF requirements' has been queued to stable release 20.11.2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to stable release 20.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 06/14/21. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/steevenlee/dpdk This queued commit can be viewed at: https://github.com/steevenlee/dpdk/commit/5d30751003cf9cff56438b0a88dfd3ac185caa74 Thanks. Xueming Li --- >From 5d30751003cf9cff56438b0a88dfd3ac185caa74 Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Tue, 11 May 2021 22:57:36 +0200 Subject: [PATCH] doc: remove PDF requirements Cc: Luca Boccassi [ upstream commit 428eaeb822c229d92e287322c80eeb15e0b53351 ] The documentation is generated in HTML only. The PDF format is abandoned since DPDK 20.11 while dropping support of the make-based build. This decision has been mentioned by the Technical Board: https://mails.dpdk.org/archives/dev/2021-January/195549.html Fixes: 3cc6ecfdfe85 ("build: remove makefiles") Signed-off-by: Thomas Monjalon Reviewed-by: Ruifeng Wang --- devtools/checkpatches.sh | 3 +- doc/guides/conf.py | 43 ------------- doc/guides/contributing/documentation.rst | 74 +++-------------------- 3 files changed, 11 insertions(+), 109 deletions(-) diff --git a/devtools/checkpatches.sh b/devtools/checkpatches.sh index 78a408ef98..db4c7d8301 100755 --- a/devtools/checkpatches.sh +++ b/devtools/checkpatches.sh @@ -118,8 +118,7 @@ check_forbidden_additions() { # -f $(dirname $(readlink -f $0))/check-forbidden-tokens.awk \ "$1" || res=1 - # svg figures must be included with wildcard extension - # because of png conversion for pdf docs + # SVG must be included with wildcard extension to allow conversion awk -v FOLDERS='doc' \ -v EXPRESSIONS='::[[:space:]]*[^[:space:]]*\\.svg' \ -v RET_ON_FAIL=1 \ diff --git a/doc/guides/conf.py b/doc/guides/conf.py index c22caaa247..894d81ca75 100644 --- a/doc/guides/conf.py +++ b/doc/guides/conf.py @@ -5,8 +5,6 @@ from docutils import nodes from distutils.version import LooseVersion from sphinx import __version__ as sphinx_version -from sphinx.highlighting import PygmentsBridge -from pygments.formatters.latex import LatexFormatter from os import listdir from os import environ from os.path import basename @@ -30,7 +28,6 @@ stop_on_error = ('-W' in argv) project = 'Data Plane Development Kit' html_logo = '../logo/DPDK_logo_vertical_rev_small.png' -latex_logo = '../logo/DPDK_logo_horizontal_tag.png' if LooseVersion(sphinx_version) >= LooseVersion('3.5'): html_permalinks = False else: @@ -49,46 +46,6 @@ feature_str_len = 30 # Figures, tables and code-blocks automatically numbered if they have caption numfig = True -latex_documents = [ - ('index', - 'doc.tex', - '', - '', - 'manual') -] - -# Latex directives to be included directly in the latex/pdf docs. -custom_latex_preamble = r""" -\usepackage{textalpha} -\RecustomVerbatimEnvironment{Verbatim}{Verbatim}{xleftmargin=5mm} -\usepackage{etoolbox} -\robustify\( -\robustify\) -""" - -# Configuration for the latex/pdf docs. -latex_elements = { - 'papersize': 'a4paper', - 'pointsize': '11pt', - # remove blank pages - 'classoptions': ',openany,oneside', - 'babel': '\\usepackage[english]{babel}', - # customize Latex formatting - 'preamble': custom_latex_preamble -} - - -# Override the default Latex formatter in order to modify the -# code/verbatim blocks. -class CustomLatexFormatter(LatexFormatter): - def __init__(self, **options): - super(CustomLatexFormatter, self).__init__(**options) - # Use the second smallest font size for code/verbatim blocks. - self.verboptions = r'formatcom=\footnotesize' - -# Replace the default latex formatter. -PygmentsBridge.latex_formatter = CustomLatexFormatter - # Configuration for man pages man_pages = [("testpmd_app_ug/run_app", "testpmd", "tests for dpdk pmds", "", 1), diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst index a4e6be6aca..1e998fd214 100644 --- a/doc/guides/contributing/documentation.rst +++ b/doc/guides/contributing/documentation.rst @@ -8,7 +8,7 @@ DPDK Documentation Guidelines This document outlines the guidelines for writing the DPDK Guides and API documentation in RST and Doxygen format. -It also explains the structure of the DPDK documentation and shows how to build the Html and PDF versions of the documents. +It also explains the structure of the DPDK documentation and how to build it. Structure of the Documentation @@ -136,17 +136,11 @@ Building the Documentation Dependencies ~~~~~~~~~~~~ - The following dependencies must be installed to build the documentation: * Doxygen. - * Sphinx (also called python-sphinx). -* TexLive (at least TexLive-core and the extra Latex support). - -* Inkscape. - `Doxygen`_ generates documentation from commented source code. It can be installed as follows: @@ -158,7 +152,7 @@ It can be installed as follows: # Red Hat/Fedora. sudo dnf -y install doxygen -`Sphinx`_ is a Python documentation tool for converting RST files to Html or to PDF (via LaTeX). +`Sphinx`_ is a Python documentation tool for converting RST files to HTML. For full support with figure and table captioning the latest version of Sphinx can be installed as follows: .. code-block:: console @@ -177,43 +171,6 @@ For further information on getting started with Sphinx see the To get full support for Figure and Table numbering it is best to install Sphinx 1.3.1 or later. -`Inkscape`_ is a vector based graphics program which is used to create SVG images and also to convert SVG images to PDF images. -It can be installed as follows: - -.. code-block:: console - - # Ubuntu/Debian. - sudo apt-get -y install inkscape - - # Red Hat/Fedora. - sudo dnf -y install inkscape - -`TexLive `_ is an installation package for Tex/LaTeX. -It is used to generate the PDF versions of the documentation. -The main required packages can be installed as follows: - -.. code-block:: console - - # Ubuntu/Debian. - sudo apt-get -y install texlive-latex-extra texlive-lang-greek - - # Red Hat/Fedora, selective install. - sudo dnf -y install texlive-collection-latexextra texlive-greek-fontenc - -`Latexmk `_ is a perl script -for running LaTeX for resolving cross references, -and it also runs auxiliary programs like bibtex, makeindex if necessary, and dvips. -It has also a number of other useful capabilities (see man 1 latexmk). - -.. code-block:: console - - # Ubuntu/Debian. - sudo apt-get -y install latexmk - - # Red Hat/Fedora. - sudo dnf -y install latexmk - - Build commands ~~~~~~~~~~~~~~ @@ -225,16 +182,7 @@ To build the documentation:: See :doc:`../linux_gsg/build_dpdk` for more detail on compiling DPDK with meson. -The output is generated in the ``build`` directory:: - - build/doc - |-- html - | |-- api - | +-- guides - | - +-- pdf - +-- guides - +The output is generated in the directories ``build/doc/html/{api,guides}``. .. Note:: @@ -259,7 +207,8 @@ Here are some guidelines in relation to the style of the documentation: RST Guidelines -------------- -The RST (reStructuredText) format is a plain text markup format that can be converted to Html, PDF or other formats. +The RST (reStructuredText) format is a plain text markup format +that can be converted to HTML or other formats. It is most closely associated with Python but it can be used to document any language. It is used in DPDK to document everything apart from the API. @@ -282,9 +231,8 @@ Line Length words. Multiple sentences which are not separated by a blank line are joined automatically into paragraphs. -* Lines in literal blocks **must** be less than 80 characters since - they are not wrapped by the document formatters and can exceed the page width - in PDF documents. +* Lines in literal blocks should be less than 80 characters + since they are not wrapped by the document formatters. Long literal command lines can be shown wrapped with backslashes. For example:: @@ -437,8 +385,8 @@ Code and Literal block sections * The default encoding for a literal block using the simplified ``::`` directive is ``none``. -* Lines in literal blocks must be less than 80 characters since they can exceed the page width when converted to PDF documentation. - For long literal lines that exceed that limit try to wrap the text at sensible locations. +* Lines in literal blocks should be less than 80 characters. + For long literal lines, try to wrap the text at sensible locations. For example a long command line could be documented like this and still work if copied directly from the docs:: .//app/dpdk-testpmd -l 0-2 -n3 --vdev=net_pcap0,iface=eth0 \ @@ -503,7 +451,7 @@ Tables ~~~~~~ * RST tables should be used sparingly. - They are hard to format and to edit, they are often rendered incorrectly in PDF format, and the same information + They are hard to format and to edit, and the same information can usually be shown just as clearly with a definition or bullet list. * Tables in the documentation should be formatted as follows: @@ -533,8 +481,6 @@ Tables The QOS configuration is shown in :numref:`table_qos_pipes`. -* Tables should not include merged cells since they are not supported by the PDF renderer. - .. _links: -- 2.25.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2021-06-12 06:53:59.245622000 +0800 +++ 0102-doc-remove-PDF-requirements.patch 2021-06-12 06:53:56.460000000 +0800 @@ -1 +1 @@ -From 428eaeb822c229d92e287322c80eeb15e0b53351 Mon Sep 17 00:00:00 2001 +From 5d30751003cf9cff56438b0a88dfd3ac185caa74 Mon Sep 17 00:00:00 2001 @@ -4,0 +5,3 @@ +Cc: Luca Boccassi + +[ upstream commit 428eaeb822c229d92e287322c80eeb15e0b53351 ] @@ -14 +16,0 @@ -Cc: stable@dpdk.org @@ -107 +109 @@ -index 842549a4c8..6098663896 100644 +index a4e6be6aca..1e998fd214 100644