From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from tiger.gg3.net (142.13.111.219.st.bbexcite.jp [219.111.13.142]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j411RsCS029792 for ; Sun, 1 May 2005 01:27:55 GMT Received: (qmail 4129 invoked by uid 1000); 1 May 2005 10:27:54 +0900 Date: Sun, 1 May 2005 10:27:53 +0900 From: Georgi Georgiev To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: The usefulness of test in FEATURES Message-ID: <20050501012753.GA2924@tiger.gg3.net> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20050430134818.GO8632@kfk4ever.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-Archives-Salt: c50d4971-1683-4300-9bd9-25ff3309dd96 X-Archives-Hash: efe27bfdeea972fd3abaf3ef7312408a maillog: 30/04/2005-13:43:42(-0600): R Hill types > Maybe a way of lessening the annoyance of test failures would be having > a way to resume the build at the install phase. I'm thinking of > something similar the touch ${BUILDDIR}/.compiled trick. as it is, if > you remove test from FEATURES, touch .tested, and then 'ebuild > foo.ebuild install' the tests still run. This is especially frustrating > when you've just spent 6 hours compiling a package to have it fail > because of sandboxing. You probably also need to edit ${T}/environment for the ebuild and remove test from FEATURES there as well. In fact, this is *the* location that you should probably touch. -- -* Georgi Georgiev -* Winning isn't everything, but losing isn't -* *- chutz@gg3.net *- anything. *- -* +81(90)2877-8845 -* -* -- gentoo-dev@gentoo.org mailing list