Alex Schuster wrote:
Jarry writes:
On 15-Nov-11 20:36, Andrey Moshbear wrote:
On Tue, Nov 15, 2011 at 13:58, Jarry<mr.ja...@gmail.com> wrote:
today I upgraded gcc from 4.4.5 to the last stable version
But at the and I noticed gcc 4.4 has not been unmerged
and my "world" file is somehow larger. To my surprise,
it contains these lines:
sys-devel/gcc
sys-devel/gcc:4.4
Because your forgot the -1 / --oneshot flag when manually upgrading gcc.
Hm, I always thought "--oneshot" was not necessary when
doing update. Even "Gentoo GCC Upgrade Guide" says just
"emerge -u gcc" (or "emerge -uav gcc" in DE-version).
The option "--oneshot" is used there only for libtool.
And I'm pretty sure I've never used "--oneshot" when
updating any packages, yet they have never been added
to world-file...
Nope. Just try again with a small package, as I just did, emerge -u will
add it to the world file. This has not always been the case, but it has
been changed at least some years ago. I'm using the newest portage, but
I believe the stable portage works the same.
Wonko
I tested this and it does add it to the world file.
root@fireball / # emerge -uv kwrite
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 kB
* kde-base/kwrite
>>> Recording kde-base/kwrite in "world" favorites file...
>>> Jobs: 0 of 0 complete Load avg: 0.76,
0.39, 0.30
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
root@fireball / #
Then this:
root@fireball / # cat /var/lib/portage/world | grep kwrite
kde-base/kwrite
root@fireball / #
Is this a bug? Just because you update a package doesn't mean you want
it in the world file.
Maybe a I need to set --oneshot in make.conf and just use -n when I
really want something in the world file.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
