On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote:
Asking developers to proxy takes almost as much time as it does to
ask them to maintain a package by themselves.
wrong
The developer is
directly responsible for anything he commits, so he will have to still
test the ebuild, still test
On 3/23/06, Daniel Goller [EMAIL PROTECTED] wrote:
On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote:
Asking developers to proxy takes almost as much time as it does to
ask them to maintain a package by themselves.
wrong
The developer is
directly responsible for anything he
On Thu, 2006-03-23 at 18:34 -0500, Dan Meltzer wrote:
On 3/23/06, Daniel Goller [EMAIL PROTECTED] wrote:
On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote:
Asking developers to proxy takes almost as much time as it does to
ask them to maintain a package by themselves.
wrong
Jonathan Coome posted
[EMAIL PROTECTED], excerpted below,
on Wed, 22 Mar 2006 10:49:29 +:
Taking this idea a bit further, what about proxy maintainers? There seem
to be quite a few packages that are being effectively maintained by
users on bugzilla, but are not in portage because they
On 3/22/06, Duncan [EMAIL PROTECTED] wrote:
A possible alternative that could be rolled out sooner would be some form
of contrib eclass. Make it a simple matter to inherit contrib and get
the standard contrib warnings and handling. One thing the eclass could
handle would be a USE=contrib
A developer could then take these ebuilds, make sure they
don't do anything malicious, or break QA, or whatever, and act as the
bridge between the portage tree and the users actually working on the
ebuild and keeping things up to date and working.
The easiest way to handle contrib as far
The process for getting unstable ebuilds from bugzilla to portage could
even be automated to the extent that when an ebuild is put into
bugzilla it gets auto committed to the tree but masked unstable.
I don't think that auto committing user submitted ebuilds is safe,
even if they are masked.
Asking developers to proxy takes almost as much time as it does to
ask them to maintain a package by themselves. The developer is
directly responsible for anything he commits, so he will have to still
test the ebuild, still test any revisions, and still follow the
package to make sure there are
On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote:
Asking developers to proxy takes almost as much time as it does to
ask them to maintain a package by themselves. The developer is
directly responsible for anything he commits, so he will have to still
test the ebuild, still test any
