| 1 |
On Fri, 2006-06-09 at 11:01 +0100, Edward Catmur wrote: |
| 2 |
> > Hmmm. I think an overlay does have some advantages there ... |
| 3 |
> |
| 4 |
> Advantages? With bugzilla I: search for the bug, cc myself on it, |
| 5 |
> download the relevant files, look over them, note a style error, try to |
| 6 |
> merge it, fix a compilation bug, re-upload the fixed ebuild and patch to |
| 7 |
> bugzilla with a comment to the ebuild author on their mistake. When an |
| 8 |
> update hits my inbox I can go directly to the bug... |
| 9 |
> |
| 10 |
> With an overlay: search sunrice.gentoo.org for the package (no, I don't |
| 11 |
> know category/name), sync that directory (no, I'm not syncing the whole |
| 12 |
> sunrice tree), check it over, note some mistakes, compile it if I feel |
| 13 |
> OK with it, it fails, I fix it - and what then? Where do I discuss the |
| 14 |
> problems? How do I get my fixes to other users, considering the package |
| 15 |
> is devless and the b.g.o bug is out of date? If I open a b.g.o bug, will |
| 16 |
> it be read? |
| 17 |
> |
| 18 |
> This seems like *raising* the barrier to entry to me... |
| 19 |
|
| 20 |
Thank you. This explains my point about no longer having a definitive |
| 21 |
place to look for things much better than I did, and from a user |
| 22 |
point-of-view no less. |
| 23 |
|
| 24 |
-- |
| 25 |
Chris Gianelloni |
| 26 |
Release Engineering - Strategic Lead |
| 27 |
x86 Architecture Team |
| 28 |
Games - Developer |
| 29 |
Gentoo Linux |
Archives