From: "Marty E. Plummer" <hanetzer@startmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] eclass/java-utils-2: switch to eapi7-ver
Date: Fri, 22 Feb 2019 20:51:12 -0600 [thread overview]
Message-ID: <20190223025111.6iokyq2z3gjhhroy@proprietary-killer> (raw)
In-Reply-To: <1801787.GisAbXGV1V@tuxbrain>
On Thu, Feb 21, 2019 at 03:30:32PM +0100, Andreas Sturmlechner wrote:
> On Montag, 17. Dezember 2018 09:09:13 CET Marty E. Plummer wrote:
> > @@ -15,7 +15,7 @@
> > # you should inherit java-pkg-2 for Java packages or java-pkg-opt-2 for
> > packages # that have optional Java support. In addition you can inherit
> > java-ant-2 for # Ant-based packages.
> > -inherit eutils versionator multilib
> > +inherit eutils multilib
>
> I would recommend to keep inheriting all those eclasses (including
> versionator) for EAPI 0-6, in order not to break revdeps with implicit use.
> Who knows in what shape they are, and no one is going to fix them for a long
> time. But we don't want to inherit any of them with EAPI-7, hence merge it
> with below hunk.
>
Yeah, I came to the same conclusion when I suggested a move from
versionator to eapi7-ver for gnome.org.eclass and it had implicit deps
on versionator in its consumers.
> > @@ -25,6 +25,9 @@ export WANT_JAVA_CONFIG="2"
> > # Prefix variables are only available for EAPI>=3
> > has "${EAPI:-0}" 0 1 2 && ED="${D}" EPREFIX= EROOT="${ROOT}"
> >
> > +# EAPI 7 has version functions built-in. Use eapi7-ver for all earlier
> > eclasses.
> > +[[ ${EAPI} == [0123456] ]] && inherit eapi7-ver
> > +
> > # @VARIABLE: JAVA_PKG_E_DEPEND
> > # @INTERNAL
> > # @DESCRIPTION:
>
>
> Regards,
> Andreas
>
>
>
prev parent reply other threads:[~2019-02-23 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:09 [gentoo-dev] [PATCH] eclass/java-utils-2: switch to eapi7-ver Marty E. Plummer
2019-02-21 14:30 ` Andreas Sturmlechner
2019-02-23 2:51 ` Marty E. Plummer [this message]
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=20190223025111.6iokyq2z3gjhhroy@proprietary-killer \
--to=hanetzer@startmail.com \
--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