From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: vapier@gentoo.org, tools-portage@gentoo.org,
"Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 1/2] app-portage/eclass-manpages: Add @SUPPORTED-EAPIS tag for eclass
Date: Fri, 28 Apr 2017 16:43:10 +0200 [thread overview]
Message-ID: <20170428144311.18082-1-mgorny@gentoo.org> (raw)
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 8ff9f71a2022..681a567af043 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 @@
# <optional; description of how to report bugs;
# default: tell people to use bugs.gentoo.org>
# @VCSURL: <optional; url to vcs for this eclass; default: https://gitweb.gentoo.org/repo/gentoo.git/log/eclass/@ECLASS@>
+# @SUPPORTED-EAPIS: <optional; space-separated list of EAPIs>
# @BLURB: <required; short description>
# @DESCRIPTION:
# <optional; long 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
next reply other threads:[~2017-04-28 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:43 Michał Górny [this message]
2017-04-28 14:43 ` [gentoo-dev] [PATCH 2/2] python-r1.eclass: Declare @SUPPORTED-EAPIS (example) Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170428144311.18082-1-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tools-portage@gentoo.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox