Question on new ebuilds handling on bugs.gentoo.org

Bobbie · Tux's lil' helper Joined: 21 Jul 2002 Posts: 77

I'd like to have some clarification on how new ebuilds submitted by users on bugs.gentoo.org are handled.

1. when are new ebuilds are integrated into the main portage tree by gentoo developpers ? It looks to me it can take forever since some old ebuilds fro; several months are still not integrated. I understand new ebuilds are not the priorirty in these times of 1.4 testing though.
I did some xmms plugins 2 months (lirc-xmms) just to see someone submitted an ebuild for it some time earlier but since it was not in the portage tree I thought it didn't existed so i made one. Same thing with FlightGear.

IMHO an entry in the FAQ should be added that say that if an ebuild does not exist, to look at bugs.gentoo.org to see it it exist. there is 90% chance it does. it may seem obvious to many but was not to me...

2. now a question on updated packages : with the problem on new ebuilds taking so long to be integrated, how some existing ebuilds are updated so fast ? (take example of quakeforge 0.5.2 for which the ebuild was updated just after it came out). Since (i believe ) only official dev gentoo members have access to update the portage tree does that mean only ebuilds maintained by them get updated quickly ? What happend to updated packages by unknown users and submitted to bugs.gentoo.org ?

rac · Posted: Sun Oct 06, 2002 9:01 pm Post subject:

I believe there is a freeze on adding new ebuilds to the tree until 1.4 is released. Bugfixes to existing ebuilds are given priority so that 1.4 can be released quicker. Once 1.4 is released and the freeze thaws, I expect that you will see relatively rapid integration of ebuilds that are sitting in bugzilla. Your suggestion about an addition to the FAQ is a good one: if you would care to submit it to Forum FAQ, we'll try to get it included. Maybe I will write it up if you don't and I remember.
_________________
For every higher wall, there is a taller ladder

Bobbie · Tux's lil' helper Joined: 21 Jul 2002 Posts: 77

I submitted it to the developper FAQ (see https://bugs.gentoo.org/show_bug.cgi?id=8860)

but maybe it would be good to add it to the forum FAQ as well

progster · Apprentice Joined: 16 Jul 2002 Posts: 271

btw shouldn't there come a better system for posting new ebuilds? posting them on bugzilla feels kinda odd...

~Progster

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

Curious · Posted: Tue Oct 08, 2002 1:23 am Post subject:

Kumba · Posted: Tue Oct 08, 2002 2:15 am Post subject:

I was wondering this as well. I submitted an ebuild for sparc64 for Silo 1.2.6 (It's Silo 1.2.5's ebuild renamed to reflect 1.2.6), yet silo-1.2.6 has been masked in the portage tree for quite some time. I figure after 1.4 is out, that'll finally get integrated now.

--Kumba
_________________
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

Starfox · Tux's lil' helper Joined: 04 Sep 2002 Posts: 93

Maybe it would be handy to implement a feature in portage, that recognizes if masked ebuilds succeses on the current configuration (hardware, CFLAGS etc.), and all these are tracked by one main gentoo site!?!??

So it would be possible to "report" (for the paranoid this may be disabled!) testing activities to the main developers, and they have the chance to release ebuild without testing them all theirselfes!!!