From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Nasty bugs in portage?
Date: Sat, 10 Sep 2005 23:03:08 +0200 [thread overview]
Message-ID: <200509102303.08309.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <1126375769.5733.59.camel@localhost.localdomain>
On Saturday 10 September 2005 20:09, Frank Schafer wrote:
> ... or which distribution to install during less than 4 days?
>
> Hi list,
>
> as I wrote yesterday I planned to complete installation after work
> (started ``emerge --emptytree system'' in the morning).
>
where did you get the idea that --emptytree is needed or even a wise decision?
--emptytree is almost NEVER needed and since it is a troublesom procedure, it
should not be made, until you are totally sure, that you need it.
emerge system
is all you need to do, to get the base system.
After that, emerge what you like to have, but NEVER use --emptytree, except
when you are able to deal with the consequences.
Obviously you are not, so do not do it.
NO
was that clear enough?
For your gcc-problem, there is the fix script, others mentioned - but a lot of
times all that is needed is to run gcc-config to set the correct gcc.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-10 21:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 18:09 [gentoo-user] Nasty bugs in portage? Frank Schafer
2005-09-10 18:37 ` Dave Nebinger
1987-12-31 23:18 ` Frank Schafer
2005-09-10 19:26 ` John Jolet
2005-09-10 19:33 ` Frank Schafer
2005-09-10 21:08 ` Zac Medico
2005-09-10 19:39 ` Dave Nebinger
2005-09-10 19:49 ` Frank Schafer
2005-09-10 20:09 ` Neil Bothwick
2005-09-10 20:13 ` Neil Bothwick
2005-09-10 19:42 ` Justin Patrin
2005-09-10 19:47 ` Frank Schafer
2005-09-10 21:03 ` Volker Armin Hemmann [this message]
2005-09-11 6:33 ` Nick Rout
2005-09-11 9:04 ` Neil Bothwick
2005-09-11 16:38 ` Volker Armin Hemmann
2005-09-11 16:58 ` Mark Shields
2005-09-11 17:12 ` Volker Armin Hemmann
2005-09-11 17:49 ` Zac Medico
2005-09-11 18:12 ` Dave Nebinger
2005-09-11 18:18 ` Zac Medico
2005-09-11 18:30 ` Dave Nebinger
2005-09-11 19:51 ` Zac Medico
2005-09-11 21:56 ` Neil Bothwick
2005-09-11 19:15 ` John Jolet
2005-09-11 19:27 ` Dave Nebinger
2005-09-11 21:57 ` Neil Bothwick
2005-09-11 22:24 ` John Jolet
2005-09-11 23:15 ` Neil Bothwick
2005-09-11 23:49 ` Nick Rout
2005-09-12 7:27 ` Neil Bothwick
2005-09-13 20:42 ` Andrew MacKenzie
2005-09-12 0:59 ` John Jolet
2005-09-12 7:31 ` Neil Bothwick
2005-09-11 23:39 ` Nick Rout
2005-09-12 7:00 ` Frank Schafer
2005-09-12 16:32 ` Volker Armin Hemmann
2005-09-11 17:45 ` Neil Bothwick
2005-09-11 19:16 ` Holly Bostick
2005-09-11 22:01 ` Neil Bothwick
2005-09-12 7:11 ` Frank Schafer
2005-09-12 7:33 ` Neil Bothwick
2005-09-12 7:52 ` Frank Schafer
2005-09-12 22:31 ` Dave Nebinger
2005-09-13 10:53 ` Frank Schafer
2005-09-11 23:51 ` Nick Rout
2005-09-12 6:56 ` Frank Schafer
2005-09-12 9:12 ` Michael Schreckenbauer
2005-09-12 9:20 ` Frank Schafer
2005-09-12 17:53 ` Volker Armin Hemmann
2005-09-14 1:45 ` Nick Rout
2005-09-14 2:21 ` Volker Armin Hemmann
2005-09-12 6:39 ` [gentoo-user] [WORKAROUNDED]Nasty " Frank Schafer
2005-09-11 15:05 ` [gentoo-user] Nasty " Hans-Werner Hilse
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=200509102303.08309.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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