1 |
I agree this would be a very nice feature and could be kept on the |
2 |
gentoo.org site as a list of ebuilds in progress, email address of |
3 |
developer, and status. This could at least allow people to try and |
4 |
contact the person who has started the ebuild, and decide whether they |
5 |
want to try and do there own, help with the current one, or wait for it |
6 |
to be completed. |
7 |
|
8 |
Sean |
9 |
|
10 |
|
11 |
-----Original Message----- |
12 |
From: Alexander Gretencord [mailto:arutha@×××.de] |
13 |
Sent: Friday, May 31, 2002 07:07 |
14 |
To: gentoo-dev@g.o |
15 |
Subject: Re: [gentoo-dev] Hard Work for ARGGHH... (Future ebuild List) |
16 |
|
17 |
|
18 |
On Friday 31 May 2002 15:52, hanez wrote: |
19 |
> is it possible to make a list under gentoo.org where all the gentoo |
20 |
> devs are making entries of there ebuilds and maybe the |
21 |
> completion-status, they are working on at the moment? |
22 |
|
23 |
I've had something similar. I made an ebuidl which was put into |
24 |
"resolved |
25 |
later" state because the dev's had no time. Then some time later another |
26 |
|
27 |
ebuild for the same software gets in. I didn't even notice because noone |
28 |
|
29 |
marked my ebuild as outdated or anything. I just noticed because some |
30 |
other |
31 |
dev saw my old ebuild and marked it as old when he saw it hanging around |
32 |
|
33 |
while some newer ebuild got in. |
34 |
|
35 |
I think this should be really improved. Also if someone makes an ebuild |
36 |
check |
37 |
if there is one in bugzilla already and then check your ebuild in under |
38 |
the |
39 |
same bug id as a new version or make a pointer to the old one. |
40 |
|
41 |
|
42 |
Alex |
43 |
|
44 |
-- |
45 |
"They that can give up essential liberty to obtain a little temporary |
46 |
safety |
47 |
deserve neither liberty nor safety." |
48 |
Benjamin Franklin _______________________________________________ |
49 |
gentoo-dev mailing list |
50 |
gentoo-dev@g.o |
51 |
http://lists.gentoo.org/mailman/listinfo/gentoo-dev |