From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: vapier@gentoo.org, tools-portage@gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] app-portage/eclass-manpages: Add @SUPPORTED_EAPIS tag for eclass
Date: Fri, 28 Apr 2017 16:31:41 +0200 [thread overview]
Message-ID: <1493389901.3838.2.camel@gentoo.org> (raw)
In-Reply-To: <20170428140604.2264-1-mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
On pią, 2017-04-28 at 16:06 +0200, Michał Górny wrote:
> 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 @@
> # <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>
Hmm, I'm going to resubmit this with '-' instead of '_'. The doc format
doesn't use either consistently, so there's really no point trying to
follow the worse option.
> # @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:")
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-04-28 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:06 [gentoo-dev] [PATCH 1/2] app-portage/eclass-manpages: Add @SUPPORTED_EAPIS tag for eclass Michał Górny
2017-04-28 14:06 ` [gentoo-dev] [PATCH 2/2] python-r1.eclass: Declare @SUPPORTED_EAPIS (example) Michał Górny
2017-04-28 14:31 ` Michał Górny [this message]
2017-05-03 21:34 ` [gentoo-dev] [PATCH 1/2] app-portage/eclass-manpages: Add @SUPPORTED_EAPIS tag for eclass Daniel Campbell
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=1493389901.3838.2.camel@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