public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: rich0@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Tightening EAPI rules
Date: Mon, 10 Feb 2014 15:58:23 +0100	[thread overview]
Message-ID: <20140210155823.0a394bd2@TOMWIJ-GENTOO> (raw)
In-Reply-To: <CAGfcS_nH0Gh-dFn-0XGqRMjFyc7FN+8soxmQDfpzEBTihs+j=A@mail.gmail.com>

On Mon, 10 Feb 2014 09:41:13 -0500
Rich Freeman <rich0@gentoo.org> wrote:

> On Mon, Feb 10, 2014 at 9:23 AM, Tom Wijsman <TomWij@gentoo.org>
> wrote:
> > Well, that package maintainers are called developers on Gentoo isn't
> > helping the interpretation here; regardless of how one defines
> > those, both maintainers and PM implementers have to be taken into
> > account here.
> >
> > From quick thoughts the latter are a bit more affected than the
> > former, but perhaps Patrick can highlight what he sees as a burden.
> 
> You would think, but the reason I raised the question was that
> historically every time this has come up the package manager
> maintainers usually chime in and say that they don't consider it a
> problem.  I want to do whatever I can to make them happy since we are
> so desperately in need of more of them, but...

From my limited look at the code I've done so far in the small bit of
repoman work on the Portage team, as detailed in another mail I just
sent to you on this ML, I wouldn't consider it as a problem just now.

We for example have /usr/lib/portage/pym/portage/eapi.py to easily deal
with it, it's just that such checks would drop in that file and across
the Portage source code when the versions listed in those checks are no
longer used. It's currently reasonable to have this amount of checks,
but imagine it growing to what you would need for 10 versions; that'd be
a different story, but perhaps it is too early to wonder about this now.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D


  reply	other threads:[~2014-02-10 14:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 12:43 [gentoo-dev] [RFC] Tightening EAPI rules Patrick Lauer
2014-02-10 13:03 ` Dirkjan Ochtman
2014-02-10 13:21   ` Tom Wijsman
2014-02-10 13:24     ` Dirkjan Ochtman
2014-02-10 14:23       ` Tom Wijsman
2014-02-10 14:41         ` Rich Freeman
2014-02-10 14:58           ` Tom Wijsman [this message]
2014-02-10 16:16             ` Ciaran McCreesh
2014-02-10 17:08               ` Tom Wijsman
2014-02-10 13:23 ` Anthony G. Basile
2014-02-10 13:46   ` Patrick Lauer
2014-02-10 14:07     ` Rich Freeman
2014-02-10 14:25     ` Ian Stakenvicius
2014-02-10 15:31     ` Ulrich Mueller
2014-02-10 15:42       ` Rich Freeman
2014-02-10 16:05         ` Ulrich Mueller
2014-02-10 16:26           ` Alan McKinnon
2014-02-10 20:56             ` Alec Warner
2014-02-10 21:26               ` Alan McKinnon
2014-02-10 17:20           ` Tom Wijsman
2014-02-10 17:47             ` Rich Freeman
2014-02-10 19:04     ` Lars Wendler
2014-02-10 14:35   ` Tom Wijsman
2014-02-10 15:34     ` Anthony G. Basile
2014-02-10 13:34 ` Rich Freeman
2014-02-10 13:44   ` Patrick Lauer
2014-02-10 14:52   ` Tom Wijsman
2014-02-12  5:07 ` [gentoo-dev] " Ryan Hill

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=20140210155823.0a394bd2@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rich0@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