From: Phil Brault <pr0teus@comcast.net>
To: Gentoo Developement <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Question about ACCEPT_KEYWORDS="~x86"
Date: Sun, 10 Nov 2002 16:05:47 -0500 [thread overview]
Message-ID: <1036962348.6963.1.camel@whitestar> (raw)
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
I may plan on rebuilding my system here in a few and I was wondering if
it would be wise to build the entire system using the
ACCPET_KEYWORDS="~x86" setting seeing as how that part of the portage
tree contains more concurrent software. However my main concern is
stability and it being worth it as it takes around 6 hours to build my
system. If anyone wants a sample of my make.conf I can share on request.
Thanks
--
Phil Brault
IT Specialist
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-11-10 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 21:05 Phil Brault [this message]
2002-11-11 21:15 ` [gentoo-dev] Question about ACCEPT_KEYWORDS="~x86" Chad Huneycutt
2002-11-11 21:42 ` jsmith
2002-11-12 10:07 ` Paul de Vrieze
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=1036962348.6963.1.camel@whitestar \
--to=pr0teus@comcast.net \
--cc=gentoo-dev@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