Am 31.03.2011 10:34, schrieb Pandu Poluan:
> Hello again. I hope you're not yet bored of my newbie questions...
>
> Out on a whim, I just did `emerge --update --newuse --pretend world`
> *just* before emerging the sources. I got this:
>
> [ebuild U ] sys-apps/portage-2.1.9.45 [2.1.9.25] USE="-python2%"
> [ebuild U ] sys-libs/glibc-2.11.3 [2.11.2-r3]
> [ebuild R ] sys-libs/ncurses-5.7-r3 USE="unicode* -gpm*"
> [ebuild U ] sys-libs/zlib-1.2.5-r2 [1.2.3-r1]
> [ebuild N ] app-arch/xz-utils-5.0.1 USE="nls threads -static-libs"
> [ebuild R ] sys-apps/coreutils-8.7 USE="unicode*"
> [ebuild U ] sys-devel/gcc-4.4.5 [4.4.4-r2]
> [ebuild U ] sys-apps/util-linux-2.18-r1 [2.17.2] USE="cramfs%* unicode*"
> [ebuild R ] app-arch/gzip-1.4 USE="-pic*"
> [ebuild U ] sys-apps/net-tools-1.60_p20100815160931
> [1.60_p20090728014017-r1]
> [ebuild U ] sys-apps/file-5.05 [5.04]
> [ebuild R ] sys-process/procps-3.2.8 USE="unicode*"
> [ebuild U ] net-misc/rsync-3.0.8 [3.0.7]
> [ebuild R ] sys-apps/baselayout-1.12.14-r1 USE="unicode*"
>
> Should I `emerge --update --newuse world` before emerging the sources?
>
> Rgds,
> --
> Pandu E Poluan
> ~ IT Optimizer ~
> Visit my Blog: http://pepoluan.posterous.com
Hi,
most likely you did an emerge --sync befor. There should have been a
notice like: A new version of portage is available. It is recomendet to
update portage first.
So you should run emerge -av portage first.
After this you could update gcc but since it is a minore update it
wouldn't mater.
Regards
KH
--
_
ASCII ribbon campaign ( )
against HTML e-mail X
/ \
ascii ribbon campaign - stop html mail - www.asciiribbon.org
