public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Benoit <kbenoit@opersys.com>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Christopher Korn <chris@chkorn.de>
Subject: Re: [gentoo-portage-dev] Next major version
Date: Fri, 12 Aug 2005 16:41:10 -0400	[thread overview]
Message-ID: <1123879271.23755.80.camel@localhost> (raw)
In-Reply-To: <42FCEEF2.5090603@egr.msu.edu>

On Fri, 2005-08-12 at 14:48 -0400, warnera6 wrote:
> Kristian Benoit wrote:
> > On Thu, 2005-08-11 at 14:19 -0400, Alec Warner wrote:
> > 
> >>Christopher Korn wrote:
> >>
> >>
> >>>>>Hi Jason and other folks,
> >>>>>I saw your last comment on
> >>>>>http://bugs.gentoo.org/show_bug.cgi?id=73350 about most the these
> >>>>>feature to be present in the next major version. That is really
> >>>>>great to read.
> >>>>>
> >>>>>On that subject, I'd like to have an idea about when we should
> >>>>>expect that next version.
> >>>>>
> >>>>>That said, I think it would be helpful to have a portage developper
> >>>>>site. Perhaps there is and I dont know...
> >>>>>     
> >>>>>
> >>>>
> >>>>  That would require someone writing one, so if you are
> >>>>volunteering ;)
> >>>>   
> >>>>
> >>>
> >>>
> >>>Writing is not the problem. But without (proper) information it is hard
> >>>to write a documentation or something like this. 
> >>>
> >>>
> >>>Chris
> >>> 
> >>>
> >>
> >>I had a wiki that attempted to cover portage-2.0 api documentation as 
> >>well as anything written for 2.1 but lost much of the work in a 
> >>transition from windows to linux ( I screwed up the SQl backups :) ).
> >>I thought about putting something up on the devwiki but I haven't 
> >>proposed anything because no one really likes a wiki for API docs.
> >>
> >>As for API docs, there are none at present; and there are no plans for 
> >>any stable docs, IIRC.
> >>
> >>As for a developer website, what kinds of information are you looking for?
> > 
> > 
> > Like you talked about, doc would be nice, Jason has some doc, api doc...
> > here:
> > http://dev.gentoo.org/~jstubbs/
> > but it does not look and is not official.
> > 
> > I remember, when I started using Gentoo, reading that portage is a stand
> > alone tool, it is not bind into Gentoo in anyway, someone could use it
> > on redhat, debian, lfs...
> > 
> > Back then I was using lfs so I thought portage could be the way to go on
> > lfs, but I realized that Gentoo fit my needs and I did'nt have to
> > compile everything by hand anymore and still have everything compiled by
> > my machines :) OH JOY !!!
> > 
> > But 5 years or so later, the only official place to get portage releases
> > is still in the gentoo mirrors. There is no RSS feed or anything like
> > that. I still believe that portage has the potential to be so powerful
> > that redhat, debian, ... could be building their packages using portage,
> > managing their own tree, having night build.
> > 
> > The problem is see, is that the initial portage vision (or perhaps my
> > initial vision, a vision I still have) has not been carried along with
> > it's developpement.
>    "portage-ng", as it were?  IMHO portage is a far cry from what is 
> needed for any kind of intense platform development.  I'm not going to 
> harp on it's problems; everyone already knows what they are and we have 
> people who are dedicated to working on it.  No one has seen the code 
> from portage-ng, so it was abandoned.  The goals set for 2.1 and beyond 
> seem lofty, and integrating portage into a non-gentoo environment is 
> tricky at best, even with a nicely rewritten API.  I don't see why other 
> distributions would turn to our tools when theirs work perfectly fine in 
> 90% of cases.  However, if they end up benefitting, more power to them. 
>   Thats why we are all here, is it not?

Thanks a lot for pointing that out.
I did a quick search about it, here are the results:

The page is dated from the end of 2003. The pdf has not been updated
since october 2003. According to google group, this is the 3rd time it
is mentionned in a group/mailing list this year. Everytime it was
someone saying: "you'll have to wait for portage-ng to get that". I
guest drobbins is Daniel Robbins. He probably cant work on the project
anymore.

So his there anyone still working on portage-ng ?

Kristian

> > 
> > Having an official web site, doc, ... will help getting visibility and
> > effort from the rest of the world thus we'll have better tools and
> > eventually extend portage beyond Gentoo.
> > 
> > Kristian
> > 
> 

-- 
gentoo-portage-dev@gentoo.org mailing list



  reply	other threads:[~2005-08-12 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 19:01 [gentoo-portage-dev] Next major version Kristian Benoit
2005-08-10 19:22 ` Alec Joseph Warner
2005-08-11 17:51   ` Christopher Korn
2005-08-11 18:19     ` Alec Warner
2005-08-11 21:36       ` Christopher Korn
     [not found]       ` <20050811233457.5ec9b4d7.chris@chkorn.de>
     [not found]         ` <42FBF831.5000201@egr.msu.edu>
2005-08-12  4:52           ` Christopher Korn
2005-08-12 16:04       ` Kristian Benoit
2005-08-12 18:48         ` warnera6
2005-08-12 20:41           ` Kristian Benoit [this message]
2005-08-12 22:12             ` Marius Mauch
2005-08-13 17:53         ` Brian Harring
2005-08-12 16:52       ` Kristian Benoit

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=1123879271.23755.80.camel@localhost \
    --to=kbenoit@opersys.com \
    --cc=chris@chkorn.de \
    --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