From: Pacho Ramos <pacho@gentoo.org>
To: Zac Medico <zmedico@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Is there a way to skip tests even having "FEATURES=test" in make.conf?
Date: Tue, 31 Aug 2010 18:01:44 +0200 [thread overview]
Message-ID: <1283270505.25797.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4C7D19CD.6070901@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
El mar, 31-08-2010 a las 08:03 -0700, Zac Medico escribió:
> On 08/31/2010 05:14 AM, Pacho Ramos wrote:
> > Hello
> >
> > Let me explain my problem:
> >
> > I have just returned to my home and, then, I have a lot of packages to
> > update when running "emerge -avuDN world". The problem is that I have
> > FEATURES=test enabled in my make.conf and, since some of them take years
> > to run, I would like to temporally make portage skip them.
> >
> > I have tried to simply disable that FEATURE temporally, but it causes
> > packages to change their USEs to "-test" having me to recompile them
> > later again.
>
> In order to avoid that, a usually suggest to enable USE=test in
> make.conf so that it's enabled regardless of the FEATURES=test state.
>
Silly me! It was so simple... :-O, thanks a lot!
> BTW, in the latest 2.2_rc releases there's support for
> /etc/portage/package.env which can be used to enable or disable
> FEATURES=test for specific packages. The package.env support will
> also be included in portage-2.1.9 which I plan to release sometime
> this week.
Nice! Thanks a lot for your work (and for the work of other portage team
members of course)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-08-31 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 12:14 [gentoo-portage-dev] Is there a way to skip tests even having "FEATURES=test" in make.conf? Pacho Ramos
2010-08-31 15:03 ` Zac Medico
2010-08-31 16:01 ` Pacho Ramos [this message]
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=1283270505.25797.9.camel@localhost.localdomain \
--to=pacho@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=zmedico@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