From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31940 invoked by uid 1002); 26 Jun 2003 14:49:38 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 27129 invoked from network); 26 Jun 2003 14:49:38 -0000 From: foser To: gentoo-dev@gentoo.org In-Reply-To: <1056617848.3025.10.camel@amd.vsen.dk> References: <1056617848.3025.10.camel@amd.vsen.dk> Content-Type: text/plain Message-Id: <1056639141.22323.52.camel@rivendell> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 26 Jun 2003 16:52:21 +0200 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] turck-mmcache ebuild X-Archives-Salt: 8282e7e7-7697-42f3-8f89-487dac9a4665 X-Archives-Hash: c39480453a3bc05bd79460aceb96317a On Thu, 2003-06-26 at 10:57, Klavs Klavsen wrote: > It's on bugs.gentoo.org. Thats where it should go. > I was wondering how these ebuilds go about getting added? as of now, > it's in a Works For Me State (and works - fine I've just upgraded the > ebuild so the newest version is there too) - and I would very much like > to see it included in the three. I'm certain there are many people who > could use this - and it's a very simple ebuild, and I'd gladly support > and continuously update it. I'm not sure this is documented anywhere, but this is not really the place for your question if it is. Or it should be documented somewhere. The bug will get assigned to a group or individual who takes care of similar ebuilds and will get audited and added if no problems arise in any way. This process may take some time, depends on how high profile the application is and how bug loaded the developer is. The herds system is a proposed way to improve ensured maintenance of ebuilds, where groups of developers are directly responsible for certain ebuilds (unlike the situation currently where everyone can touch everything to a certain degree (hey you, stay off the gnome ebuilds ;)). There is currently no formal way to have non-official devs maintain directly their submitted ebuilds, you are of course free to keep the relevant developers up-to-date with improved ebuilds and version notices via bugzilla or maybe use IRC or email to interact with the responsible developer(s) directly. - foser -- gentoo-dev@gentoo.org mailing list