1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Johannes Weiner wrote: |
5 |
> One more tab in ${BROWSER}.. And it shouldn't make more work. It should |
6 |
> ease the work already there. |
7 |
> Having submitted an outdated port seems to be more comfortable to me |
8 |
> than checking your portrepo everyday for actuality. |
9 |
|
10 |
What it seems like you're doing here is saying more work for the |
11 |
developers is fine, if it makes things easier for the users. (Developers |
12 |
will just cvs up, which is likely faster than dealing with a web interface.) |
13 |
|
14 |
Although that may be nice in concept, in reality developers may have |
15 |
quite limited time. Most things that detract from the time they spend on |
16 |
development rather than on searching around and figuring out what to do |
17 |
makes Gentoo worse. It has yet to be proven that your suggestion would |
18 |
take more time, but that's the feeling I have. |
19 |
|
20 |
If one knows how to search bugzilla and understands how maintainers are |
21 |
indicated, this can be comparably easy already. Something like this |
22 |
could give you a search: |
23 |
|
24 |
1. Use herdstat to find the maintainer, if you aren't comfortable with |
25 |
the metadata.xml files. |
26 |
|
27 |
$ herdstat --metadata xorg-x11 |
28 |
Package: x11-base/xorg-x11 |
29 |
Herds(1): x11 |
30 |
Maintainers(0): none |
31 |
Homepage: http://xorg.freedesktop.org/ |
32 |
Description: X11 implementation by X.Org Foundation |
33 |
|
34 |
2. Search for Enhancement bugs assigned to that herd/maintainer in |
35 |
Bugzilla. In this case, it would be bugs assigned to x11@g.o. |
36 |
|
37 |
3. Profit! |
38 |
|
39 |
Thanks, |
40 |
Donnie |
41 |
-----BEGIN PGP SIGNATURE----- |
42 |
Version: GnuPG v1.4.1 (GNU/Linux) |
43 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
44 |
|
45 |
iD8DBQFCkmKxXVaO67S1rtsRArXJAJ4gx6G+v4CJkXxx2NCd6ZN1Yw/aBgCfTrGl |
46 |
2wOH333zS11rgRLePRM3jxw= |
47 |
=GV1a |
48 |
-----END PGP SIGNATURE----- |
49 |
-- |
50 |
gentoo-dev@g.o mailing list |