From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Cc: <vincent.primavera@ralphpill.com>
Subject: RE: [gentoo-user] USE flags...
Date: Mon, 18 Jul 2005 11:38:34 -0400 [thread overview]
Message-ID: <005d01c58bae$c2fd2eb0$5f01010a@jnetlab.lcl> (raw)
In-Reply-To: <00c801c58bac$cbc94c10$0501a8c0@DELVAPBOS>
> I'm trying to avoid a big, bloated system without going too crazy here.
> Any suggestions?
Your problem is going to be the incremental enabling thing you'd like to do.
If you add a new USE flag later on, you need to emerge with the newuse flag
which will result in a larger emerge than what you expect.
For example, if you build your system then add the alsa use flag and emerge
with newuse, you'll basically be rebuilding X, kde and/or gnome, etc. A
huge task for such a simple flag addition.
Your best bet is to determine the use flags that you intend on using in the
final system and be selective about what you emerge to keep the system size
under control.
Unless, of course, you don't mind recompiling big parts of the system for
use case changes...
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 15:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 15:24 [gentoo-user] USE flags Vincent A. Primavera
2005-07-18 15:38 ` Dave Nebinger [this message]
2005-07-18 15:53 ` Rumen Yotov
2005-07-18 17:17 ` Marco Matthies
-- strict thread matches above, loose matches on Subject: below --
2005-07-18 16:58 Vincent A. Primavera
2005-07-18 17:24 ` Vincent A. Primavera
2005-08-20 0:46 John Dangler
2005-08-20 1:50 ` Marco Matthies
2005-08-20 2:19 ` John Dangler
2005-08-20 2:26 ` John Jolet
2005-08-20 2:37 ` Marco Matthies
2005-08-20 3:53 ` Walter Dnes
2005-08-20 13:48 ` Peter O'Connor
2005-10-24 22:13 Eric Waguespack
2005-10-24 22:19 ` Hemmann, Volker Armin
2005-10-24 22:21 ` Dave Nebinger
2005-10-24 22:21 ` Holly Bostick
2005-10-24 22:22 ` Petteri Räty
2005-10-24 22:24 ` Brett I. Holcomb
2005-10-25 15:24 ` Neil Bothwick
2005-10-25 19:55 ` Mark Shields
2005-10-25 23:58 ` Neil Bothwick
2005-10-24 22:29 ` Willie Wong
2005-10-24 23:11 ` Holly Bostick
2005-12-02 20:14 Jeff
2005-12-02 20:58 ` Neil Bothwick
2005-12-02 21:02 ` Dale
2005-12-02 22:20 ` John J. Foster
2006-03-09 11:19 Goran Maksimoviæ
2006-03-09 16:29 ` Daniel da Veiga
2006-03-09 17:15 ` Richard Fish
2006-03-09 18:22 ` Goran Maksimović
2006-03-10 1:52 ` Boyd Stephen Smith Jr.
2006-04-05 14:28 Leonid Podolny
2006-12-10 9:35 [gentoo-user] USE Flags Vlad Dogaru
2006-12-10 9:46 ` Raymond Lewis Rebbeck
2006-12-10 9:55 ` Uwe Thiem
2006-12-10 11:20 ` Neil Bothwick
2006-12-10 16:18 ` Vlad Dogaru
2006-12-10 17:34 ` Rick van Hattem
2012-07-25 16:55 [gentoo-user] Use Flags Silvio Siefke
2012-07-25 17:07 ` Yohan Pereira
2012-07-26 6:42 ` Alan McKinnon
2012-07-26 13:22 ` Allan Gottlieb
2012-07-26 18:53 ` 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='005d01c58bae$c2fd2eb0$5f01010a@jnetlab.lcl' \
--to=dnebinger@joat.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=vincent.primavera@ralphpill.com \
/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