public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Tom Wijsman <TomWij@gentoo.org>, cbergstrom@pathscale.com
Subject: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team)
Date: Sun, 19 Jan 2014 03:25:38 -0500	[thread overview]
Message-ID: <201401190325.39433.vapier@gentoo.org> (raw)
In-Reply-To: <20140113155345.07d9feb7@TOMWIJ-GENTOO>

[-- Attachment #1: Type: Text/Plain, Size: 1699 bytes --]

On Monday 13 January 2014 09:53:45 Tom Wijsman wrote:
> On Mon, 13 Jan 2014 16:15:37 +0700 "C. Bergström" wrote:
> > At the end of the day we have one codebase which is
> > "engineered" and another which has "evolved".
> 
> Too broad generalization, too much assumption; both can be held as
> meaning nothing compared to what "engineered" and "evolved" could
> really be, but as with doing that, it gets a subjective nature.
> 
> In other words, the lack of context makes this statement meaningless.

anyone who has spent serious time in the portage code base knows it sucks.  
i'm not blaming anyone -- it's no one's fault.  portage started as prototyped 
idea that has since had more and more stuff piled onto it over the years by 
each successive maintainer.  devs i've talked to agree that it sucks to work 
with.  it's why pkgcore was born in the first place.

i'd like to see portage & pkgcore merge, but it'd take quite a bit of work on 
the portage side to migrate step by step.  we generally haven't had leads who 
have enough time sorting out the existing bugs/feature requests to try and 
also restructure/reshape things.  maybe by trying to get new interest in the 
project means we can find some people willing to rip off some sizable chunks.  
the fact that the public API is pretty much non-existent is nice because it 
means we're free to change/break whatever we want.

note though that the "let's rewrite everything in a branch and then merge 
later" approach doesn't work.  it's been done a few times in portage land and 
aborted each time.  it's rare for this to work for other projects either.  
small steps are much easier to review/merge.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-01-19  8:25 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
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 [this message]
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=201401190325.39433.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=TomWij@gentoo.org \
    --cc=cbergstrom@pathscale.com \
    --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