1 |
hmmm...I never intended to imply that the ebuild repository and bugs |
2 |
wouldn't be integrated....only that the avg joe downloader wouldn't be |
3 |
forced to learn a developer tool and that the ebuild repository would |
4 |
automatically push issues into the bugs database. |
5 |
|
6 |
To take this step up another notch, when bugs are fixed for a particular |
7 |
package, the issues surrounding the bug are suppressed to just a link |
8 |
called "past bugs" but when a bug is actively open, then the issues for |
9 |
that bug are displayed prominently for the end user so he can quickly |
10 |
determine if the package is going to meet his needs. |
11 |
|
12 |
This is something that would be most important to me as a new Linux |
13 |
user...I'm trying to find |
14 |
good quality packages and I know little about their background, but if I |
15 |
can read comments about them and see that there are bug issues at the |
16 |
moment, I can choose to move on to another package or attempt to work |
17 |
around the known bug issues. |
18 |
|
19 |
Michael |
20 |
At 01:26 AM 3/17/2002 +0100, you wrote: |
21 |
>On Saturday 16 March 2002 23:09, Brent Cook wrote: |
22 |
> > Do you essentially mean http://www.freshports.org/ with |
23 |
> > comments? |
24 |
> |
25 |
>that's cool, but imho there should be some way to leverage |
26 |
>bugs.gentoo.org by integrating both. i think it would be an |
27 |
>overkill having a separate "ebuild repository", it should rather |
28 |
>be kept central. |
29 |
> |
30 |
>probably a simple link like |
31 |
> |
32 |
>http://bugs.gentoo.org/buglist.cgi?component=Ebuilds |
33 |
> |
34 |
>(add your date constraints) |
35 |
> |
36 |
>would be sufficient if we just agreed on a standardized way how |
37 |
>ebuild submissions (and error reports) have to be made. this |
38 |
>could be done by "forcing" a formatted summary field. e.g. for |
39 |
>ebuild submissions: |
40 |
> |
41 |
>${P} ${DESCRIPTION} |
42 |
> |
43 |
>this would be suitable for most users (as gentoo mainly targets |
44 |
>developers/professionals and as the ebuild names are usually |
45 |
>self-explanatory). disclaimer: i do not know whether forcing |
46 |
>field formats is possible with bugzilla. a voting feature |
47 |
>would be nice too. |
48 |
> |
49 |
>rgds |
50 |
> |
51 |
>dan |
52 |
> |
53 |
>-- |
54 |
> ...::: Daniel Mettler | http://www.numlock.ch :::.... |
55 |
> |
56 |
>_______________________________________________ |
57 |
>gentoo-dev mailing list |
58 |
>gentoo-dev@g.o |
59 |
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
60 |
|
61 |
President |
62 |
www.cybrains.net |
63 |
|
64 |
"All things should be as simple as possible, but no simpler" -- Albert Einstein |