On Wednesday 01 June 2005 23:58, Jonathan Stickel wrote: > Matias Grana wrote: > >>First an ebuild needs to be made and submitted to bugs.gentoo.org. > >>This you should be able to do. Next, that bug needs to catch the > >>interest of a developer, and if he/she likes it, it will get into > >>portage. From my experience, this rarely happens with low profile > >>programs. > >> > >>Jonathan > > > > doesn't look very promising :( Anyway, I just built it. I'll play with > > it and if I find it interesting and useful I'd eventually try to produce > > the ebuild. At least, it should be a learning experience :-) > > Yes, and anyone can pull ebuilds from the bugs database. This way your > effort can be helpful to others even if it never makes it into portage.
We do look at the bugs assigned, and get an email for anything assigned to [EMAIL PROTECTED] There is also #gentoo-science on freenode. There are currently 249 bugs in the sci queue, and there are only a few of us to take care of them. > > > Now, suppose I get to convince a developer that this is a good thing to > > add to portage. In this case, who is in charge of mask/unmask the > > program, keep it up to date, etc.? > > My understanding is that only developers can commit changes like > architecture keywords, updated ebuilds, etc. However, anyone can submit > version updates through the bugs system. Generally the developer or herd takes care of the ebuild, and they commit updated ebuilds. Architecture teams take care of keywording on other architectures - I am also a member of the AMD64 porting team for example. I do prefer to work in partnership with interested parties to maintain ebuilds. It is a case of picking the ebuilds that look most useful and relevant, and also being able to test their functionality reasonably before adding it to portage. I for example have a degree in Physics, and am currently studying for my PhD in the same area - so I have quite a lot of expertise in that area. As such I tend to leave biology type programs to people like Olivier who know a lot more than I do in that area, but will happily tackle mathematics, astronomy, graphing packages, statistical/mathematical languages, symbolic computing, AFM, circuit design and that kind of stuff. I hope this makes it clearer to you. We are all volunteers and so only have a limited amount of time to take care of all the bugs. I always try to track this mailing list and the sci@ alias as do many other members of the herd. Marcus -- Gentoo Linux Developer Scientific Applications | AMD64 | KDE | net-proxy
pgpxeQ9aMlNdx.pgp
Description: PGP signature
