From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32140 invoked from network); 29 Dec 2003 22:52:16 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 29 Dec 2003 22:52:16 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1Ab6FE-0002Kp-M9 for arch-gentoo-dev@lists.gentoo.org; Mon, 29 Dec 2003 22:52:16 +0000 Received: (qmail 2904 invoked by uid 50004); 29 Dec 2003 22:34:09 +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 4466 invoked from network); 29 Dec 2003 22:34:09 +0000 Date: Mon, 29 Dec 2003 17:34:13 -0500 From: Jason Wever To: gentoo-dev@lists.gentoo.org Message-Id: <20031229173413.55c9924e@enterprise.weeve.org> In-Reply-To: <20031229040040.GC9146@tompayne.org> References: <20031229040040.GC9146@tompayne.org> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Mon__29_Dec_2003_17_34_13_-0500_9QV=wKgqudl6_lN4" Subject: Re: [gentoo-dev] Re: Please do not stabilize packages for arches you cannot test for X-Archives-Salt: 3b06b90a-730a-4fad-9a41-58bb2e9c6056 X-Archives-Hash: e2a8548f8fd6f7a0a4e2e49e138c46aa --Signature=_Mon__29_Dec_2003_17_34_13_-0500_9QV=wKgqudl6_lN4 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Mon, 29 Dec 2003 04:00:40 +0000 Tom Payne wrote: > Problems solved: > > Arch leads no longer have to test every single ebuild that comes there > way-- non x86 arches get package updates quicker with reduced workload > for arch leads. If we can do this without a loss of the Q in QA, then I'm all for it :) One alternative that is becoming available to developers are the development/release engineering boxes that are cropping up. For a lot of programs out there, it's not hard to test their functionality remotely (though GUI applications can be a bit harder). I imagine having one or two people per herd with accounts on these various boxes would help improve QA substantially. Granted at the current time, not all arches have a publically available test machine or two, but it definitely decreases the amount of work on the arch devs and the "no news is good news" stablization of ebuilds that happens now. > No need to write unit tests for packages to help arch leads (lots of > work and hard to do in some cases (e.g. interactive progs)). Test cases don't necessarily need to be automated. A simple list of instructions to verify functionality that a dev could run wound be acceptable (to me). For example 1) Do operation a 2) Do operation b 3) Expect result c > New problems: > > Might result in broken software being installed. I'd like to avoid this if at all possible. All software in the tree, even if it's marked ~arch, is supposed to work. The fact that ~arch things are broken is bad, but if a package gets to arch broken or still broken is even worse, and reflects poorly on Gentoo as a whole. > Feedback please. I advocate this approach for 'minor' packages, i.e. > nothing fundamental to the working of the system. It's more suitable for > scripting language libraries and minor applications (e.g. obscure window > managers). While most of the time, packages aren't problematic on non-x86 arches, there do crop up those that have abnormal behavior. Whether it's unable to compile or has undesired/broken functionality once compiled/installed. I'm a bit more open to packages that are scripts, but I have yet to meet a language that is truly as cross-platform compatible as they all claim to be (not that I'm any kind of official reviewer or have run into every language out there). However, if something like this is implemented, I would ask that programs that need to be compiled not be put into this list. If a problem is going to crop up, it'll be here, and often times Makefiles don't fail correctly if something cannot build (for instance try over-optimizing net-firewall/fwbuilder and then find the fwbuilder executable after it has installed). My (non-refundable) $0.02, -- Jason Wever Gentoo/Sparc Team Co-Lead --Signature=_Mon__29_Dec_2003_17_34_13_-0500_9QV=wKgqudl6_lN4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQE/8KvldKvgdVioq28RAuq2AJ46SlzpmNsp1Z2XzWibCtYSOfTJbgCfQlZ7 V2Te8Fyuvk8ci3jFtFRxlVw= =Kckg -----END PGP SIGNATURE----- --Signature=_Mon__29_Dec_2003_17_34_13_-0500_9QV=wKgqudl6_lN4--