public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marty E. Plummer" <hanetzer@startmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] eclass: freedict: require EAPI=6
Date: Mon, 26 Mar 2018 17:58:19 -0500	[thread overview]
Message-ID: <20180326225818.fvg6narho5pacw4f@proprietary-killer.fossland> (raw)
In-Reply-To: <1522101480.23621.8.camel@gentoo.org>

On Mon, Mar 26, 2018 at 11:58:00PM +0200, Michał Górny wrote:
> W dniu pon, 26.03.2018 o godzinie 16∶33 -0500, użytkownik Marty E.
> Plummer napisał:
> > As a pretty simple eclass, which only inherited multilib in
> > order to get $(get_libdir) and eutils for who knows why, and
> > all its consumers bumped to EAPI=6, it makes sense to require
> > EAPI 6 for this eclass
> > 
> 
> It's trivial, used by 6 ebuilds... why do we even have this eclass?
> 
> If I wrote mgorny.eclass it would have more consumers ;-P.
>
Possibly, but it does allow for pretty quick additions of freedict
packages, but since everything that uses it is EAPI 6 now it makes
sense to go ahead and ban lesser EAPIs in order to prevent their
reintroduction in that category. Honestly if you could set EAPI in
an eclass I'd set it there, then every ebuild using it would be at
EAPI 6 to begin with :)


  reply	other threads:[~2018-03-26 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 21:33 [gentoo-dev] [PATCH] eclass: freedict: require EAPI=6 Marty E. Plummer
2018-03-26 21:58 ` Michał Górny
2018-03-26 22:58   ` Marty E. Plummer [this message]
2018-03-27  9:20 ` Ulrich Mueller
2018-03-28  7:31   ` Marty E. Plummer
2018-03-28  8:52     ` Ulrich Mueller
2018-04-04  8:04       ` Marty E. Plummer
2018-04-04 11:28         ` Aaron Bauman
2018-04-04 12:20           ` Ulrich Mueller
2018-04-04 11:58             ` Marty E. Plummer

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=20180326225818.fvg6narho5pacw4f@proprietary-killer.fossland \
    --to=hanetzer@startmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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