public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC - Gentoo on the Lab
Date: Mon, 22 Aug 2005 15:39:10 -0500	[thread overview]
Message-ID: <20050822203910.GS10816@nightcrawler> (raw)
In-Reply-To: <1124732954.6502.61.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]

On Mon, Aug 22, 2005 at 01:49:14PM -0400, Kristian Benoit wrote:
> On Mon, 2005-08-22 at 16:38 +0200, Marius Mauch wrote:
> 
> > Anyway, I hope you realize that your project doesn't only involve
> > hacking on portage, but rewriting almost all of it for the client part.
> > Actually I'd rather suggest you start from scratch
> 
> I do agree with that, portage probably need a rewrite/better
> modularization anyway. There is/was a project called portage-ng () you
> might want to have a look at. I did a little in that direction recently,
> and it seems that there is not too many people working on it since
> drobbins left, but you can contact Pieter (pvdabeel@gentoo.org). I might
> get on that too at some point in the future too.

Portage-ng never resulted in anything tangible (read: code), further 
the doc wasn't really useful for anything then jotting down what's 
desired.  Unless something's changed, that doc should've been yanked 
down.  She's dead, jim.

Regarding modularization of portage, it requires that, but 
fundamentally it requires a rewrite of the core; there is no internal 
package abstraction, repository abstraction, hell, even a clean config 
abstraction (let alone cache abstraction).

The 2.1 code that was pushed out for inspection addresses the cache 
issue mostly, and modularization as much as possible.  Everything else 
falls to the rewrite which is underway- I'd suggest contacting portage 
devs, since what you're after is pretty much what's been designed to 
allow for, without requiring hacks to portage- just would be plugins.

That and help would always be welcome :P
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-22 20:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  1:58 [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22  2:12 ` Andrew Gaffney
2005-08-22  3:34 ` Donnie Berkholz
2005-08-22 10:05   ` Ivan Yosifov
2005-08-22 11:31   ` [gentoo-dev] " Duncan
2005-08-22 13:26     ` Ricardo Loureiro
2005-08-22 23:57       ` [gentoo-dev] " Duncan
2005-08-22 14:38 ` [gentoo-dev] " Marius Mauch
2005-08-22 15:35   ` Ricardo Loureiro
2005-08-22 16:57     ` Grobian
2005-08-22 17:49   ` Kristian Benoit
2005-08-22 20:39     ` Brian Harring [this message]
2005-08-23 16:25       ` Kristian Benoit
2005-08-23 17:22         ` Brian Harring
2005-08-23 17:27         ` Brian Harring
2005-08-23 22:58           ` Kristian Benoit
2005-08-25  0:50             ` [gentoo-dev] portage rewrite snapshot (was RFC - Gentoo on the Lab) Brian Harring
2005-08-23 16:45       ` [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 20:41     ` Stephen Bennett
2005-08-23 16:28       ` Kristian Benoit
2005-08-23 17:19         ` Brian Harring
2005-08-23 16:34       ` Ricardo Loureiro
2005-08-23 17:28         ` Marius Mauch

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=20050822203910.GS10816@nightcrawler \
    --to=ferringb@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