From: William Hubbs <williamh@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage performance dropped considerably
Date: Sun, 26 Jan 2014 17:26:19 -0600 [thread overview]
Message-ID: <20140126232619.GA9429@laptop.home> (raw)
In-Reply-To: <52E556F0.3040908@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
On Sun, Jan 26, 2014 at 07:41:52PM +0100, hasufell wrote:
> Starting with USE="-*" on a server (which is a sane thing to do) has
> become a lot more difficult as well.
No, starting with USE="-*" is very dangerous. It is not recommended nor
supported, in any setup, by the dev community. If you do it, you are
solely responsible for your system and you get to keep the broken pieces
when things do not work.
A safer approach would be to turn off the specific use flags you do not
want to support.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-26 23:26 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 14:35 [gentoo-user] Portage performance dropped considerably Nikos Chantziaras
2014-01-26 14:44 ` hasufell
2014-01-26 14:50 ` [gentoo-user] " Remy Blank
2014-01-26 15:24 ` eroen
2014-01-26 17:42 ` Alan McKinnon
2014-01-26 18:04 ` hasufell
2014-01-26 18:30 ` Alan McKinnon
2014-01-26 18:41 ` hasufell
2014-01-26 19:22 ` Alan McKinnon
2014-01-26 20:44 ` ny6p01
2014-01-27 5:03 ` Alan McKinnon
2014-01-27 9:27 ` Neil Bothwick
2014-01-26 23:26 ` William Hubbs [this message]
2014-01-26 23:36 ` Andreas K. Huettel
2014-01-27 0:44 ` Andreas K. Huettel
2014-01-27 11:44 ` hasufell
2014-01-28 1:34 ` Martin Vaeth
2014-01-28 3:19 ` hasufell
2014-01-28 17:45 ` Martin Vaeth
2014-01-28 18:07 ` hasufell
2014-01-29 14:24 ` Kerin Millar
2014-01-28 0:41 ` Walter Dnes
2014-01-28 1:42 ` Martin Vaeth
2014-01-28 4:02 ` Walter Dnes
2014-01-31 19:03 ` Andrew Savchenko
2014-01-31 19:13 ` Mick
2014-01-31 21:18 ` Andrew Savchenko
2014-01-31 22:12 ` Alan McKinnon
2014-02-02 9:40 ` Andrew Savchenko
2014-02-03 10:55 ` Martin Vaeth
2014-02-03 11:57 ` Greg Turner
2014-02-03 13:17 ` Martin Vaeth
2014-01-26 19:29 ` Volker Armin Hemmann
2014-01-26 19:45 ` Alan McKinnon
2014-01-26 20:10 ` Volker Armin Hemmann
2014-01-27 9:30 ` Neil Bothwick
2014-01-27 11:59 ` Tanstaafl
2014-01-27 13:06 ` Alan McKinnon
2014-01-27 13:57 ` hasufell
2014-01-27 21:48 ` Neil Bothwick
2014-01-27 21:54 ` hasufell
2014-01-27 22:57 ` Neil Bothwick
2014-01-27 23:35 ` hasufell
2014-01-28 1:35 ` Neil Bothwick
2014-02-03 14:04 ` Pandu Poluan
2014-02-03 14:16 ` Alan McKinnon
2014-02-03 16:38 ` Pandu Poluan
2014-02-04 5:12 ` Martin Vaeth
2014-01-28 1:50 ` Martin Vaeth
2014-01-30 3:50 ` hasufell
2014-01-30 18:15 ` [gentoo-user] " Stroller
2014-01-31 20:08 ` hasufell
2014-01-26 19:28 ` [gentoo-user] " Volker Armin Hemmann
2014-01-26 19:55 ` Alan McKinnon
2014-01-27 12:06 ` Helmut Jarausch
2014-01-27 21:56 ` Stefan G. Weichinger
2014-01-26 15:53 ` [gentoo-user] " Mariusz Ceier
2014-01-31 17:23 ` Andrew Savchenko
2014-01-26 16:06 ` Florian Philipp
2014-01-26 16:15 ` hasufell
2014-01-26 17:52 ` Florian Philipp
2014-01-26 18:16 ` covici
2014-03-07 19:36 ` Tom Wijsman
-- strict thread matches above, loose matches on Subject: below --
2014-01-26 15:09 Greg Turner
2014-01-26 15:32 ` [gentoo-user] " eroen
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=20140126232619.GA9429@laptop.home \
--to=williamh@gentoo.org \
--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