| 1 |
On Thu, 2006-10-05 at 08:34 +0200, Natanael Copa wrote: |
| 2 |
> If the "proxy maintainer" is specified as contact person in the ebuild, |
| 3 |
> and will be added to the CC list on bugs posted, the official developer |
| 4 |
> will not need to care about it until he gets a response from the proxy |
| 5 |
> developer. |
| 6 |
|
| 7 |
Well, look at sys-auth/bioapi. The ebuild is written (and maintained) |
| 8 |
by an ex-developer, SeJo. He sends me the updates, and I commit them. |
| 9 |
About the only thing that I do is run them through repoman and check |
| 10 |
that they're not doing fun things like "rm -rf /" in pkg_preinst. ;] |
| 11 |
|
| 12 |
Of course, they're super-new, so there's no bugs, but once a bug gets |
| 13 |
filed on it, I'll be sure that SeJo is added to CC, if he isn't added by |
| 14 |
the bug wrangler. At that point, I'll expect him to fix it. In the |
| 15 |
end, *I* am ultimately responsible for the package, since I am the |
| 16 |
developer that "maintains" it, but the workload on me is minimal, at |
| 17 |
most. |
| 18 |
|
| 19 |
> But I'd like to do official portage and not any overlay. I have |
| 20 |
> submitted ebuilds to bugzilla that ended up in an overlay somehwere (bug |
| 21 |
> got closed) and has dissapeared for ever. I can't post bugs about |
| 22 |
> overlays in bugzilla, (I suppose) so no updated ebuild have been |
| 23 |
> submitted and I ended up just running my own local overlay. |
| 24 |
|
| 25 |
If your package was added to an overlay and the bug was closed, it was |
| 26 |
closed in error. Bug reports (unless they pertain to an overlay itself) |
| 27 |
don't get closed until the bug is "FIXED" in the main tree. |
| 28 |
|
| 29 |
-- |
| 30 |
Chris Gianelloni |
| 31 |
Release Engineering Strategic Lead |
| 32 |
Alpha/AMD64/x86 Architecture Teams |
| 33 |
Games Developer/Council Member/Foundation Trustee |
| 34 |
Gentoo Foundation |
Archives