On Wed, Jan 21, 2004 at 11:19:15AM +0100, John Nilsson wrote: > Recently there was a thread about cvs access for non-devs the following > problems were highlighted. > > 1. Users frustrated by not beeing able to work on ebuilds. > 2. Devs not wanting bad ebuilds in the tree. > > I think this can be adressed. > I'm just learning how RCS works so excuse me if this sound stupid, just > correct me =). > > Why not have a cvs (or svn) tree where non-core-dev ebuilds is worked upon, > a free for all tree, (or some minimum registration, recognition...). When > a dev feels like the ebuild is usable: branch it (i gather this is what > you do in cvs, in svn you just make a copy). > > There should also be a tree which is write-protected to single users ie "/ > path/to/RCS/home/someone/" so that I can trust that all files in that tree > comes from a single trusted source. > > Now devs and non-devs just merge back and forth as development proceed. > > 1. User frustration somewhat lower as development participation at least > feels higher. > 2. The official part of the tree is still untouched by non-devs. > 3. A way to update /usr/local/portage in an easy, semi-trusted way. > > #svn co http://rcs.gentooserver.com/home/IamtheOne/portage > /usr/local/portage > #emerge sync > #cd /usr/local/portage && svn up > #emerge -u world > >
And millions of bug reports from users who don't realize they shouldn't report bugs to us on unofficial, unsupported ebuilds, plus users who don't realize Gentoo isn't responsible for any breakage, viruses, or whatever else propogated by an unofficial tree. Definitely not something I would ever be in favor of hosting on Gentoo infrastructure or supporting in any way, personally. -- Jon Portnoy avenj/irc.freenode.net -- [EMAIL PROTECTED] mailing list
