From: Tom Wijsman <TomWij@gentoo.org>
To: chutzpah@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage QOS
Date: Fri, 10 Jan 2014 03:40:22 +0100 [thread overview]
Message-ID: <20140110034022.0599901c@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20140109175216.5c558257@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
On Thu, 9 Jan 2014 17:52:16 -0800
Patrick McLean <chutzpah@gentoo.org> wrote:
> On Fri, 10 Jan 2014 02:19:03 +0100
> Tom Wijsman <TomWij@gentoo.org> wrote:
>
> > Or rather: "What does it take to migrate parts of pkgcore into
> > portage?"
>
> Why not just switch to using pkgcore as the default package manager.
Has anyone switched to pkgcore already?
It needs to work well and be wide tested before it can become a default.
> radhermit has been doing a lot of work lately getting EAPI 5 support
> added, and generally fixing bugs etc.
Are we there yet?
The thing about pkgcore is that it is perceived as running behind; and
with the lack of interest in it due to that, it seems that having it
will take some time before it lifts off the ground. Don't get me wrong,
it eventually will if we pursue it; but, when? It can take time.
> Since we no longer have anyone intimately familiar with the
> portage code, we should just switch to a more modern and readable
> system.
Agreed, but we also should keep Portage alive and kicking until then.
> Rather than having random people trying to learn the
> convoluted portage code, let's concentrate on getting pkgcore to a
> point where we can replace portage with it.
Either way, people need to learn something; and if we can't guarantee
the short term future of Portage before pkgcore becomes usable, the
long term future could rather be out of reach before you know it.
In the short term we should focus on Portage, but in the long term we
should indeed look at one or another replacement; and indeed does
pkgcore soon appear to be the most interesting option here.
To satisfy QA and Portage teams at the same time; I'm going to start
digging into repoman soon as there are 80+ bugs open for it, so in the
short term (days / weeks), I have no plans for pkgcore myself.
From there on I plan to do a software re-engineering style inspection on
the Portage base to learn and understand its convoluted structure; at
that point we can make more educated choices as to which way to go
forward, but until then ... let's just fix as much bugs as time permits.
Don't get me wrong; pkgcore is great, but it takes time for attention
to shift to it as Portage's slowly runs into more legacy code problems.
--
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-10 2:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 7:24 [gentoo-dev] Portage QOS LTHR
2014-01-09 8:12 ` Alec Warner
2014-01-09 12:44 ` Igor
2014-01-09 14:12 ` Christopher Schwan
2014-01-09 15:26 ` Igor
2014-01-09 15:55 ` Jeroen Roovers
2014-01-09 16:37 ` Igor
2014-01-10 0:27 ` heroxbd
2014-01-10 12:41 ` Igor
2014-01-10 13:51 ` Rich Freeman
2014-01-10 0:16 ` heroxbd
2014-01-10 0:31 ` Patrick Lauer
2014-01-10 1:19 ` Tom Wijsman
2014-01-10 1:52 ` Patrick McLean
2014-01-10 2:40 ` Tom Wijsman [this message]
2014-01-10 6:17 ` Brian Dolbec
2014-01-10 18:14 ` Ciaran McCreesh
2014-01-10 7:54 ` heroxbd
2014-01-10 18:11 ` Ciaran McCreesh
2014-01-11 3:57 ` Patrick Lauer
2014-01-10 1:02 ` Tom Wijsman
2014-01-10 9:10 ` heroxbd
2014-01-10 14:54 ` Tom Wijsman
2014-01-10 12:23 ` Igor
2014-01-10 12:30 ` René Neumann
2014-01-10 12:30 ` Igor
2014-01-10 12:39 ` Patrick Lauer
2014-01-10 13:05 ` Igor
2014-01-10 13:18 ` René Neumann
2014-01-10 18:19 ` Ciaran McCreesh
2014-01-10 19:06 ` René Neumann
2014-01-10 14:05 ` heroxbd
2014-01-12 10:47 ` [gentoo-dev] " Steven J. Long
2014-01-10 13:10 ` [gentoo-dev] " Igor
2014-01-10 14:02 ` Rich Freeman
2014-01-10 15:16 ` Tom Wijsman
2014-01-10 18:12 ` Ciaran McCreesh
2014-01-09 15:49 ` Ben Kohler
2014-01-09 16:11 ` Igor
2014-01-09 17:59 ` [gentoo-dev] " Duncan
2014-01-09 20:42 ` Igor
2014-01-09 21:08 ` Chris Reffett
2014-01-10 12:10 ` Igor
2014-01-10 12:26 ` René Neumann
2014-01-10 12:52 ` Igor
2014-01-10 12:57 ` René Neumann
2014-01-10 15:39 ` Tom Wijsman
2014-01-10 16:36 ` Mike Frysinger
2014-01-10 18:17 ` Greg KH
2014-01-10 19:38 ` Duncan
2014-01-10 22:36 ` heroxbd
2014-01-11 1:28 ` Duncan
2014-01-09 19:35 ` [gentoo-dev] " yac
2014-01-11 15:00 ` Naohiro Aota
2014-01-12 10:28 ` Igor
2014-01-12 19:31 ` Igor
2014-01-12 19:31 ` Igor
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=20140110034022.0599901c@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=chutzpah@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