From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Re: portage-ng roadmap?
Date: Wed, 30 Jun 2004 22:07:52 +0200 [thread overview]
Message-ID: <200406302207.52557.pauldv@gentoo.org> (raw)
In-Reply-To: <xgxargynofbet.i04n5f0.pminews@news.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
On Wednesday 30 June 2004 11:03, Adrian Gschwend wrote:
> On Tue, 29 Jun 2004 14:15:18 -0700, George Shapovalov wrote:
> >Well, what's going on is not that its "legally dead". It got its start and
> > we threw a bunch of comments on the "design". However there does not seem
> > to be much push behind it at the moment. I suspect there may be only one
> > dev working on it (pvdabeel?), if at all. However there is clearly an
> > effort to clean-up and enhance the [oroginal] portage under way.
>
> ok after all I care less about a portage-ng but about something I can use
> on non-Linux platforms :-) Is pvdabeel also reading this list?
I don't know. Currently I'm working on my own effort on a portage rewrite. It
should follow most of the ideas that have been floating around for ng, but I
cannot give any time on delivery of a useable system. The only thing that I
have really working well now is searching (emerge -s) which is a lot faster.
Further I've developed an ebuild parser in c++ which still has issues. If
there is a lot of interest I might put it in gentoo cvs or release a tarbal.
However as I'm going away in 8 days I think that will happen only in a month.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-30 20:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 8:44 [gentoo-portage-dev] portage-ng roadmap? Adrian Gschwend
2004-06-28 14:08 ` Marius Mauch
2004-06-28 22:55 ` Roman Gaufman
2004-06-29 7:52 ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-29 18:44 ` Hasan Khalil
2004-06-29 21:15 ` George Shapovalov
2004-06-30 9:03 ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30 9:07 ` John Nilsson
2004-06-30 9:24 ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30 20:07 ` Paul de Vrieze [this message]
2004-06-30 21:41 ` [gentoo-portage-dev] " Brian Harring
2004-06-30 22:23 ` Nathaniel McCallum
2004-07-01 9:25 ` Paul de Vrieze
2004-07-12 9:08 ` Philippe Lafoucrière
2004-07-12 9:17 ` Michael Kohl
2004-07-12 10:44 ` Brian Harring
2004-07-15 13:30 ` Paul de Vrieze
2004-07-16 7:14 ` Philippe Lafoucrière
2004-07-16 8:10 ` Paul de Vrieze
2004-07-16 8:49 ` Philippe Lafoucrière
2004-07-04 21:35 ` Pieter Van den Abeele
2004-07-05 11:05 ` [gentoo-portage-dev] " Adrian Gschwend
2004-07-05 21:24 ` Pieter Van den Abeele
2004-07-07 20:54 ` [gentoo-portage-dev] " gentoo
2004-07-07 19:49 ` [gentoo-portage-dev] unsubscribing (was: Re: portage-ng roadmap?) Andrew Gaffney
2004-06-30 9:03 ` [gentoo-portage-dev] Re: Re: portage-ng roadmap? Adrian Gschwend
2004-06-30 13:06 ` Hasan Khalil
2004-07-04 21:45 ` [gentoo-portage-dev] " Pieter Van den Abeele
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 10:04 [gentoo-portage-dev] Re: " Paul de Vrieze
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=200406302207.52557.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-portage-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