From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Tightening EAPI rules
Date: Mon, 10 Feb 2014 15:23:58 +0100 [thread overview]
Message-ID: <20140210152358.00eeb1ed@TOMWIJ-GENTOO> (raw)
In-Reply-To: <CAKmKYaCM0hPk=VVPtqf1Vt4YEQQ_VPcLkXsfuO4FLZHo_ZmdOA@mail.gmail.com>
On Mon, 10 Feb 2014 14:24:39 +0100
Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Mon, Feb 10, 2014 at 2:21 PM, Tom Wijsman <TomWij@gentoo.org>
> wrote:
> > Apart from that, they however sit in the way of deprecating support
> > for that EAPI; at one point it becomes tedious to have to support
> > 10 EAPIs in our code (eg. Portage), hence we should aim to
> > deprecate versions of a few years old. Keeping old stuff around can
> > take its toll...
>
> Sure, but Patrick was explicitly talking about a burden on developers,
> not a burden on package manager implementers.
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.
--
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
next prev parent reply other threads:[~2014-02-10 14:24 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 [this message]
2014-02-10 14:41 ` Rich Freeman
2014-02-10 14:58 ` Tom Wijsman
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=20140210152358.00eeb1ed@TOMWIJ-GENTOO \
--to=tomwij@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