From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AFFE5139694 for ; Fri, 28 Apr 2017 14:06:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5652FE0E76; Fri, 28 Apr 2017 14:06:12 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 14FFBE0E71 for ; Fri, 28 Apr 2017 14:06:12 +0000 (UTC) Received: from localhost.localdomain (d202-252.icpnet.pl [109.173.202.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 5A2F2341727; Fri, 28 Apr 2017 14:06:10 +0000 (UTC) From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Cc: vapier@gentoo.org, tools-portage@gentoo.org, =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= Subject: [gentoo-dev] [PATCH 1/2] app-portage/eclass-manpages: Add @SUPPORTED_EAPIS tag for eclass Date: Fri, 28 Apr 2017 16:06:03 +0200 Message-Id: <20170428140604.2264-1-mgorny@gentoo.org> X-Mailer: git-send-email 2.13.0.rc1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Archives-Salt: c190e526-6ba6-4fa8-bc4a-7bc05706ddcc X-Archives-Hash: 6070f5565433f6dd324a9a48a2e5d388 Add a @SUPPORTED_EAPIS tag that can be used to explicitly provide a list of EAPIs that are supported by the eclass. The main goal is to make it possible to extract this list with relative ease, for scripting purposes. It is not included explicitly in the manpages at the moment. The first use case is to make it possible to explicitly distinguish eclasses that do not support a specific EAPI from eclasses that are not used by any ebuilds using a specific EAPI. Therefore, it will make it possible to easily detect when we can deprecate old EAPIs from eclasses. --- app-portage/eclass-manpages/files/eclass-to-manpage.awk | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/app-portage/eclass-manpages/files/eclass-to-manpage.awk b/app-portage/eclass-manpages/files/eclass-to-manpage.awk index 0b65162c04ec..fe7e9c12d8f5 100644 --- a/app-portage/eclass-manpages/files/eclass-to-manpage.awk +++ b/app-portage/eclass-manpages/files/eclass-to-manpage.awk @@ -18,6 +18,7 @@ # # @VCSURL: +# @SUPPORTED_EAPIS: # @BLURB: # @DESCRIPTION: # @@ -147,6 +148,7 @@ function handle_eclass() { eclass = $3 eclass_maintainer = "" eclass_author = "" + supported_eapis = "" blurb = "" desc = "" example = "" @@ -176,6 +178,8 @@ function handle_eclass() { reporting_bugs = eat_paragraph() if ($2 == "@VCSURL:") vcs_url = eat_line() + if ($2 == "@SUPPORTED_EAPIS:") + supported_eapis = eat_line() if ($2 == "@BLURB:") blurb = eat_line() if ($2 == "@DESCRIPTION:") -- 2.13.0.rc1