From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user <Gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] stage3.1 USE flags, okay to 'ignore' differences?
Date: Sat, 20 Aug 2011 22:13:07 +0700 [thread overview]
Message-ID: <CAA2qdGWP_4+_bcgqWw5_G=nC2UyCWMJrO+abt0dOzzNMQ3s92Q@mail.gmail.com> (raw)
I hope someone can shed me some light here.
I keep finding myself doing time-consuming emerges for my Gentoo
(virtual) systems (e.g., gcc-4.5.3, glibc-2.13, emerge -e, and so on).
So, I found myself wanting to build a so-called 'stage3.1' tarball
(i.e., a stage3 tarball *plus* the things I did all this time).
Now, my systems have different USE flags, depending on its usage. So
my question is:
Can I just disregard the differences in USE flags for my stage3.1
(e.g., just use the most-minimal amount of USE flags) and do an emerge
-avuND @system @world for every system having a different set of USE
flag? Or should I make one stage3.1 tarball for each USE flag
combination?
Rgds,
--
--
Pandu E Poluan - IT Optimizer
My website: http://pandu.poluan.info/
next reply other threads:[~2011-08-20 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 15:13 Pandu Poluan [this message]
2011-08-20 15:43 ` [gentoo-user] stage3.1 USE flags, okay to 'ignore' differences? Alan McKinnon
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='CAA2qdGWP_4+_bcgqWw5_G=nC2UyCWMJrO+abt0dOzzNMQ3s92Q@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=Gentoo-user@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