From: Alexander Berntsen <alexander@plaimi.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [OT] pkgcore bikeshed
Date: Mon, 13 Jan 2014 13:28:13 +0100 [thread overview]
Message-ID: <52D3DBDD.6030205@plaimi.net> (raw)
In-Reply-To: <20140113110210.GA1993@rathaus.eclipse.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 13/01/14 12:02, Steven J. Long wrote:
> Yeah but it already outshines under the hood: all you're talking
> about is EAPI and radhermit is working on it; I'm sure he and
> dol-sen would be happy for more help as well, so long as it's
> supportive. ISTR TomWij is involved too.
I know all this. But until the EAPI is brought up to date, I don't see a
lot of devs migrating their work there. (Kudos to radhermit for his
work.) Furthermore, bringing the EAPI up to date is not of ignorable
complexity.
> Updating both in parallel isn't hard: once pkgcore is up to EAPI-5,
> EAPI-6 isn't that much work (mostly bash afair.)
If it is trivial: show us the code.
> At that point, put portage into feature-freeze, and only bugfix it.
> Call a hiatus on new EAPIs for 6 months and put all effort into
> making damn sure pkgcore is a drop-in replacement.
I don't see this happening as it stands right now. Let's revisit this
when pkgcore is more up to date.
> There's certainly enough devs to do that, and definitely enough
> interest in finally moving to portage-NG.
These are two big statements, and I'm not convinced either of them
holds true. Feel free to gather data on the latter. (The former is not
immediately quantifiable.)
- --
Alexander
alexander@plaimi.net
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlLT290ACgkQRtClrXBQc7XeuAD+Jj4Oj73br8pvcKdkDSVFfE3J
tG6ajS3wzQHNmkbxWPoA+gMVyzgm5SSDRAjqHysocgvvDe6Xwa2CA+/ON98u+2xs
=mBxD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-13 12:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 5:33 [gentoo-dev] Portage team, Zac's development break and stepping down as lead Brian Dolbec
2014-01-06 7:53 ` Dirkjan Ochtman
2014-01-06 8:27 ` Brian Dolbec
2014-01-13 3:07 ` Brian Dolbec
2014-01-13 5:05 ` Brian Dolbec
2014-01-13 8:39 ` C. Bergström
2014-01-13 8:43 ` Alexander Berntsen
2014-01-13 9:15 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) "C. Bergström"
2014-01-13 9:31 ` Fabio Erculiani
2014-01-13 9:38 ` "C. Bergström"
2014-01-13 14:58 ` Tom Wijsman
2014-01-13 15:38 ` Luis Ressel
2014-01-13 15:46 ` Tom Wijsman
2014-01-13 17:03 ` Luis Ressel
2014-01-13 18:07 ` Tom Wijsman
2014-01-13 18:05 ` Ciaran McCreesh
2014-01-13 18:19 ` Tom Wijsman
2014-01-13 16:49 ` Alec Warner
2014-01-13 17:10 ` Fabio Erculiani
2014-01-13 18:16 ` Tom Wijsman
2014-01-13 18:21 ` Ciaran McCreesh
2014-01-13 18:32 ` Tom Wijsman
2014-01-13 23:22 ` Patrick Lauer
2014-01-13 23:49 ` Tom Wijsman
2014-01-13 11:02 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Steven J. Long
2014-01-13 12:28 ` Alexander Berntsen [this message]
2014-01-13 13:06 ` Andreas K. Huettel
2014-01-13 13:50 ` Ulrich Mueller
2014-01-13 15:28 ` Tom Wijsman
2014-01-13 17:51 ` [gentoo-dev] " Ulrich Mueller
2014-01-14 7:41 ` [gentoo-dev] pkgcore EAPI-6 (Was: OT: pkgcore bikeshed) Steven J. Long
2014-01-13 15:21 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Tom Wijsman
2014-01-13 20:29 ` Donnie Berkholz
2014-01-13 14:46 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) Tom Wijsman
2014-01-13 14:56 ` Ian Stakenvicius
2014-01-13 15:31 ` Tom Wijsman
2014-01-13 18:01 ` Brian Dolbec
2014-01-13 18:07 ` Ciaran McCreesh
2014-01-13 18:27 ` Tom Wijsman
2014-01-13 18:37 ` Ciaran McCreesh
2014-01-14 7:56 ` [gentoo-dev] " Steven J. Long
2014-01-13 14:53 ` [gentoo-dev] " Tom Wijsman
2014-01-19 8:25 ` Mike Frysinger
2014-01-13 17:37 ` Greg KH
2014-01-13 17:42 ` "C. Bergström"
2014-01-13 17:56 ` Greg KH
2014-01-13 8:59 ` [gentoo-dev] Portage team, Zac's development break and stepping down as lead Dirkjan Ochtman
2014-01-13 14:42 ` Tom Wijsman
2014-01-13 14:46 ` Peter Stuge
2014-01-13 15:38 ` Tom Wijsman
2014-01-13 16:41 ` Alec Warner
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=52D3DBDD.6030205@plaimi.net \
--to=alexander@plaimi.net \
--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