From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15981 invoked from network); 23 May 2004 15:54:23 +0000 Received: from smtp.gentoo.org (156.56.111.197) by parrot.ussg.indiana.edu with SMTP; 23 May 2004 15:54:23 +0000 Received: from parrot.ussg.indiana.edu ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BRvIt-0006KN-61 for arch-gentoo-dev@lists.gentoo.org; Sun, 23 May 2004 15:54:23 +0000 Received: (qmail 30963 invoked by uid 89); 23 May 2004 15:54:11 +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 21481 invoked from network); 23 May 2004 15:54:11 +0000 Date: Sun, 23 May 2004 17:54:06 +0200 From: Karl Trygve Kalleberg To: Josh Glover Cc: gentoo-dev@lists.gentoo.org Message-ID: <20040523155406.GA1055@gentoo.org> References: <200405201846.37173.cbrewer@stealthaccess.net> <1085145580.8753.93.camel@newkid.milsson.nu> <1085146797.25036.52.camel@localhost> <200405211554.06946.c.j.bainbridge@ed.ac.uk> <1085151850.878.7.camel@gs75.geol.vt.edu> <1525.24.123.50.150.1085156959.squirrel@mail.jmglov.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <1525.24.123.50.150.1085156959.squirrel@mail.jmglov.net> User-Agent: Mutt/1.5.6i Sender: Karl Trygve Kalleberg Subject: Re: [gentoo-dev] Stuff that makes people mad X-Archives-Salt: cd9ee9c2-ca36-4262-85be-0aff3a59abc2 X-Archives-Hash: d1535f9b1f899b2f6e6f3efbc3e25428 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 21, 2004 at 12:29:19PM -0400, Josh Glover wrote: >=20 > I wonder if we can design an ebuild-lint tool to validate ebuilds > automatically. It could work something like this: >=20 > 1. User submits an ebuild to Bugzilla > 2. ebuild-lint runs on it (out of cron, maybe) > 3. If ebuild lint finds problems, the user is emailed with a laundry list= of > things to fix > 4. When ebuild-lint finds no errors with the ebuild, then and only then i= s the > ebuild brought to the attention of bug-wranglers, who would assign it = to the > proper herd. I already did this two years ago. The project was called 'munchie'. It did all kinds of sanity checks on the incoming ebuild's syntax, tried to build it, and produced a lengthy report on the quality of the ebuild. However, at the time, we were not able to integrate it with Bugzilla, don't ask me why, I wasn't part of the infrastructure team even then, so it never picked up. However, if there is renewed interest in the project, I can bring it back to life, as it still falls under my domain as a "portage tools" maintainer/developer. In the next version, I had planned a proper tinderbox, so we could do a lot more compile-time/run-time checks on it. Kind regards, Karl T --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAsMkekvv4V9zefggRAgTsAKDdDx4tqC3CKM6t32oAeBUv1OD9BQCfXj+1 eaV3rk9mcc6xxdbmglywdU0= =lntt -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--