1 |
Edward Catmur wrote: |
2 |
> On Fri, 2006-06-09 at 10:28 +0200, Patrick Lauer wrote: |
3 |
>> Instead of a simple cvs up; cd /usr/local/portage/category/package I |
4 |
>> need to search for ALL bugs with $name in it, look which one it is, |
5 |
>> curse bugzilla for falling asleep again, see which attachments are |
6 |
>> relevant, download them, curse bugzilla for falling asleep again, copy |
7 |
>> them to my overlay, read the bugcomments to see if any special renaming |
8 |
>> or directory structure is needed ... |
9 |
>> |
10 |
>> Hmmm. I think an overlay does have some advantages there ... |
11 |
> |
12 |
> Advantages? With bugzilla I: search for the bug, cc myself on it, |
13 |
> download the relevant files, look over them, note a style error, try to |
14 |
> merge it, fix a compilation bug, re-upload the fixed ebuild and patch to |
15 |
> bugzilla with a comment to the ebuild author on their mistake. When an |
16 |
> update hits my inbox I can go directly to the bug... |
17 |
|
18 |
Hmmm, I mostly notice a different scenario: |
19 |
|
20 |
- search for the bug, and file a dupe because you didn't find it :P |
21 |
- bug gets marked as a dupe |
22 |
- the guy who filed the dupe comments on how much bugzilla search sucks |
23 |
- download one of obsolete broken ebuilds attached to the bug |
24 |
- moan that it doesn't work |
25 |
- download another ebuild |
26 |
- moan that it doesn't work either |
27 |
- someone points to comment #27 that says you need to edit lines XX and |
28 |
YY for the ebuild to work |
29 |
- do it, post yet another redundant "yay, that finally worked!" comment |
30 |
- attach a "fixed" ebuild tarball |
31 |
- you get scream upon to not attach tarballs |
32 |
- you attach a plaintext ebuild now |
33 |
- notice that its MIME type is application/octet-stream |
34 |
- change the mime type |
35 |
- look at the ebuild in the browser now that you can and notice bunch of |
36 |
stupid typos you've done that ruin the whole fix (hello, Mr. Murphy) |
37 |
- try to edit the attachment in bugzilla, which produces one huge |
38 |
nonsense comment instead of actually editing the ebuild |
39 |
- attach a new one |
40 |
- oh noes, it's octet-stream again! argh! |
41 |
- fix it... |
42 |
- forgot to mark previous one as obsolete, do it now |
43 |
- produce "sorry for the noise" comment |
44 |
- someone notices that you've still left two typos there and attaches |
45 |
yet another ebuild |
46 |
|
47 |
By now, about 15 bugspams times the number of people CCed on the bug got |
48 |
sent, containing mostly useless crap. |
49 |
|
50 |
> With an overlay: search sunrice.gentoo.org for the package (no, I don't |
51 |
> know category/name), sync that directory (no, I'm not syncing the whole |
52 |
> sunrice tree), check it over, note some mistakes, compile it if I feel |
53 |
> OK with it, it fails, I fix it - and what then? Where do I discuss the |
54 |
> problems? How do I get my fixes to other users, considering the package |
55 |
> is devless and the b.g.o bug is out of date? If I open a b.g.o bug, will |
56 |
> it be read? |
57 |
> |
58 |
> This seems like *raising* the barrier to entry to me... |
59 |
|
60 |
Yes, with an overlay you can prevent all the attachment screwups noted |
61 |
above and once you are really satisfied that it works, you post a link |
62 |
to bugzilla. You can fix your typos in VCS, even multiple times, without |
63 |
bugspamming the hell out of people, and you still have the history to go |
64 |
back if you screw up. Bugs with tens of attachments are essentially |
65 |
useless for most of newcomers and suck for effective development as |
66 |
well. A couple of examples: |
67 |
|
68 |
http://bugs.gentoo.org/show_bug.cgi?id=24247 |
69 |
http://bugs.gentoo.org/show_bug.cgi?id=70161 |
70 |
http://bugs.gentoo.org/show_bug.cgi?id=122500 |
71 |
|
72 |
|
73 |
-- |
74 |
Best regards, |
75 |
|
76 |
Jakub Moc |
77 |
mailto:jakub@g.o |
78 |
GPG signature: |
79 |
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E |
80 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
81 |
|
82 |
... still no signature ;) |