| 1 |
On Friday 11 July 2003 07:40, Patrick Kursawe wrote: |
| 2 |
> On Thu, Jul 10, 2003 at 06:31:32PM +0200, Martin Lesser wrote: |
| 3 |
> > Before reporting this ebuild to bugs.gentoo.org I would like to know how |
| 4 |
> > long the "normal" period is between reporting a new ebuild and finding |
| 5 |
> > this ebuild in the portage tree (or getting any other response)- another |
| 6 |
> > ebuild was added on 05/31/03 |
| 7 |
> > (http://bugs.gentoo.org/show_bug.cgi?id=22000) but since then not much |
| 8 |
> > happened... |
| 9 |
> |
| 10 |
> I'm afraid there is nothing like a "normal" period. It depends on quite |
| 11 |
> a few factors... for example, if a developer is interested in the program, |
| 12 |
> if he thinks he will be able to maintain it, how clean the ebuild looks, |
| 13 |
> air pressure, moon phase... |
| 14 |
> |
| 15 |
> > IMO creating or reporting ebuilds which perhaps are only helpful here |
| 16 |
> > doesn't make much sense. |
| 17 |
> |
| 18 |
> Perhaps someone else who needs it will find it when searching |
| 19 |
> bugs.gentoo.org for it. Try to see it as a "user contributed ebuilds" |
| 20 |
> database aswell. |
| 21 |
|
| 22 |
Also, ebuilds that go to big projects as kde and gnome will probably take more |
| 23 |
time. There are very many kde and gnome programs with various functions. The |
| 24 |
herds project aims to divide those to more projects, so that a kde sound |
| 25 |
editor will go to the sound project, not to kde. That should help things as |
| 26 |
the members of the kde and gnome projects do not use every kind of program |
| 27 |
themselves. |
| 28 |
|
| 29 |
Paul |
| 30 |
|
| 31 |
-- |
| 32 |
Paul de Vrieze |
| 33 |
Researcher |
| 34 |
Mail: pauldv@××××××.nl |
| 35 |
Homepage: http://www.cs.kun.nl/~pauldv |
Archives