[gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable

[gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable

[Paulo Jorge de Oliveira Cantante de Matos]

Hi all,

I'd like to know more about how an ebuild that shows up in
bugs.gentoo.org goes to portage as unstable and then passes to stable.
Which are the requirements of each of these phases?

Best regards,

-- 

Paulo J. Matos : pocm@mega.ist.utl.pt
Instituto Superior Tecnico - Lisbon
Computer and Software Eng. - A.I.
 - > http://mega.ist.utl.pt/~pocm
---
        -> God had a deadline...
                So, he wrote it all in Lisp!


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable

[Chris Gianelloni]

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

On Mon, 2003-10-20 at 21:48, Paulo Jorge de Oliveira Cantante de Matos
wrote:
> Hi all,
> 
> I'd like to know more about how an ebuild that shows up in
> bugs.gentoo.org goes to portage as unstable and then passes to stable.
> Which are the requirements of each of these phases?
> 
> Best regards,

Well, generally the ebuild goes to the developer(s) whom would probably
end up being responsible for the ebuild.  For example, if you posted an
ebuild for a game, the Gentoo Games Team would get the bug.  One of the
team would take the ebuild and test it.  If the ebuild syntax looks
good, then we would add it to portage as ~arch for the architectures we
can test.  If after an unspecified period of time (usually 30-90 days)
there are no outstanding bugs for the ebuild, it then gets changed to
stable.

I know that doesn't cover every case, but that is the general way it
works.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]