| 1 |
On Tue, 2005-09-13 at 14:08 +0200, Jakub Moc wrote: |
| 2 |
> 13.9.2005, 13:39:10, Chris Gianelloni wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
> > I know that this is automatically generated, but can we either change |
| 6 |
> > the bug subjects or figure out some way to add proposed categories to |
| 7 |
> > these? I think changing the summary should suffice. For the ones with |
| 8 |
> > categories, I can pretty much figure out what they are. For the ones |
| 9 |
> > without, I have no clue and have to look at the bug to determine if I |
| 10 |
> > would even be interested in it. |
| 11 |
> |
| 12 |
> Uhm, if the ebuild submitter does not choose a category, then we'd have to |
| 13 |
> change the subject ourselves (and sometimes I'm not even remotely sure into |
| 14 |
> which category would the particular ebuild fit). |
| 15 |
|
| 16 |
Try asking the submitter? *grin* |
| 17 |
|
| 18 |
Here's a good example. If I submitted an ebuild for "nwn" what would |
| 19 |
you think it might be? What if I submitted it as "games-rpg/nwn" |
| 20 |
instead? Now, a category isn't *required* of there's a decent |
| 21 |
description (such as the "gkrellm plugin" description shown as an |
| 22 |
example). The point being that nobody is going to be able to determine |
| 23 |
what some of these packages are without some serious investigation, as |
| 24 |
they tend to have cryptic names. |
| 25 |
|
| 26 |
-- |
| 27 |
Chris Gianelloni |
| 28 |
Release Engineering - Strategic Lead/QA Manager |
| 29 |
Games - Developer |
| 30 |
Gentoo Linux |
Archives