From: Ulrich Mueller <ulm@gentoo.org>
To: Florian Schmaus <flow@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] gradle.eclass: add new eclass
Date: Wed, 28 Jun 2023 11:21:16 +0200 [thread overview]
Message-ID: <w6gwmzohrhv.fsf@uni-mainz.de> (raw)
In-Reply-To: <20230628075245.892402-2-flow@gentoo.org> (Florian Schmaus's message of "Wed, 28 Jun 2023 09:52:44 +0200")
>>>>> On Wed, 28 Jun 2023, Florian Schmaus wrote:
> +# @FUNCTION: gradle-src_uri
> +# @DESCRIPTION:
> +# Generate SRC_URI data from EGRADLE_BUNDLED_VER.
> +gradle-src_uri() {
This is named gradle_src_uri (with two underscores) in the main eclass
documentation.
> +# @FUNCTION: gradle-src_unpack
> +# @DESCRIPTION:
> +# Unpack the "bundled" gradle version. You must have
> +# EGRADLE_BUNDLED_VER set when calling this function.
> +gradle-src_unpack() {
Even if this isn't exported, is there any good reason for deviating from
the normal naming convention for eclass phase functions?
Ulrich
next prev parent reply other threads:[~2023-06-28 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 17:20 [gentoo-dev] RFC: new gradle.eclass Florian Schmaus
2023-01-06 17:20 ` [gentoo-dev] [PATCH] gradle.eclass: add new eclass Florian Schmaus
2023-01-07 4:29 ` Sam James
2023-01-07 10:58 ` Florian Schmaus
2023-01-07 6:07 ` Anna
2023-01-06 17:51 ` [gentoo-dev] RFC: new gradle.eclass Maciej Barć
2023-01-06 18:52 ` Yuan Liao (Leo)
2023-01-06 19:40 ` Florian Schmaus
2023-06-28 7:52 ` [gentoo-dev] [PATCH 0/2] " Florian Schmaus
2023-06-28 7:52 ` [gentoo-dev] [PATCH 1/2] gradle.eclass: add new eclass Florian Schmaus
2023-06-28 8:51 ` Michał Górny
2023-06-28 9:21 ` Ulrich Mueller [this message]
2023-06-28 7:52 ` [gentoo-dev] [PATCH 2/2] dev-java/openjfx: switch to gradle.eclass Florian Schmaus
2023-06-30 8:39 ` [gentoo-dev] [PATCH 0/2] new gradle.eclass Sam James
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=w6gwmzohrhv.fsf@uni-mainz.de \
--to=ulm@gentoo.org \
--cc=flow@gentoo.org \
--cc=gentoo-dev@lists.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