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