public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R Hill <dirtyepic@metawire.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: The usefulness of test in FEATURES
Date: Sun, 01 May 2005 01:27:12 -0600	[thread overview]
Message-ID: <d52019$uff$1@sea.gmane.org> (raw)
In-Reply-To: <20050501012753.GA2924@tiger.gg3.net>

Georgi Georgiev wrote:
> 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.

Cool.  So this is as simple as "sed -i -e 's@\(^FEATURES.*\) 
test\(.*$\)@\1\2@g' /var/tmp/portage/pkgname/temp/environment" then.

Thanks. =]

--de.


-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-01  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 13:48 [gentoo-dev] The usefulness of test in FEATURES Maurice van der Pot
2005-04-30 15:30 ` Rumen Yotov
2005-04-30 15:48   ` Jason Stubbs
2005-04-30 16:32     ` Rumen Yotov
2005-04-30 17:32   ` Maurice van der Pot
2005-04-30 17:45     ` Jason Stubbs
2005-04-30 17:54       ` Jason Stubbs
2005-04-30 19:43 ` [gentoo-dev] " R Hill
2005-05-01  1:27   ` Georgi Georgiev
2005-05-01  7:27     ` R Hill [this message]
2005-05-01  8:59   ` Jason Stubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='d52019$uff$1@sea.gmane.org' \
    --to=dirtyepic@metawire.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox