On Tuesday 01 February 2005 06:37 pm, Holly Bostick <[EMAIL PROTECTED]> wrote: > Nick Rout wrote: > > On Tue, 1 Feb 2005 20:30:41 +0000 > > Pupeno <[EMAIL PROTECTED]> wrote: > >>Is there a place where I can recomend/ask for an ebuild to become > >> stable (x86 instead of ~x86) ? > > bugs.gentoo.org > > > > Doesn't this to some degree depend on where the ebuild came from in the > first place? If normally from Portage, there's no reason to request that > an ~arch ebuild be made stable; afaik, that occurs normally 30 days > after it went "live", if there are no major bugs reported.
Right, but this doesn't happen automatically, AFAIK. A request on b.g.o could help, esp. if the ebuild has been forgotten. It's unlikely that an ebuild goes stable before 30 days are up, sincethat is gentoo's agreed upon timeframe for bug reports. > If, on the other hand, this is an ebuild that originally came from > b.g.o., then requesting that it be included in the regular Portage tree > might be the next step, but there appear to be quite a few ebuilds on > b.g.o which seem to be "stuck in traffic". I myself don't know what is > the process for moving such forward. Pretty much the same as any bug w/ patch. Has to get to the right herd, and then it has to be looked over and approved. Then someone with CVS access commits it. Depending on how many ebuild are avilable for the package and how extensive the ebuild is, it can take a while just to get it looked at and approved. Once in portage, the 30 day ticker applies to these equally. The herd must agree to adopt and maintain the ebuild or it won't get put into portage; just left available for people to place in their overlays, if need be. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- [email protected] mailing list
