Now you tell it, I guess that updating to XFree 4.3.0 was caused by this
>=x11-base/xfree-4.2.0-r11
in the dependencies of mozilla, and emerging it using ACCEPT_KEYWORDS="~x86" emerge mozilla.
Maybe I should have done this:
emerge /usr/portage/net-www/mozilla/mozilla-1.3.ebuildThis way I would only emerge the mozilla package itself... well, inexperience, I promise I will do better next time :o)
Paul de Vrieze wrote:
On Thursday 20 March 2003 13:19, Jose Gonzalez Gomez wrote:
I tried to emerge mozilla 1.3 yesterday, but in its dependencies
included XFree 4.3.0. I thought I'd give it a try, and I emerged it
accepting ~x86, but once I did it, Gnome didn't work. I thought about
recompiling Gnome using an ACCEPT_KEYWORDS="~x86" emerge -u world, but
after pretending, and having in mind that this is my main work box, and
I cannot have it down for a lot of time, I decided to reemerge -u world
to downgrade the installed things. So I put the computer at work before
going to bed, and this morning, after a short etc-update, my system was
working like a charm again. Man, this is really great, keep up the good
work at Gentoo.
Moz 1.3 works for me without xfree-4.3
Aside from that, the question is, do you find the "unstable" platform reasonably stable? Any experiences from the ~side? And a few question about the use of ~x86. Is (not) recommended to emerge some packages with x86 ans some others with ~x86? (I did it and Gnome stopped working because of (I guess) the new version of XFree, I guess if less "delicate" packages are involved, the results shouldn't be so "dramatic"). And what about the use of different USE settings? I think changing this and making certain things (like depclean) could wipe out needed packages. So is there any "best practices" standard?
The USE flags determine optional dependencies in packages. You can use the ufed utility to set them, or do it manually.
For me the unstable branch is too unstable with certain packages. I believe a hybrid approach is better. This is especially valid for packages that are depended upon by many others. This includes things like X, glibc, gcc, and portage. The stability of those packages can differ dramatically. Most packages are promoted to stable fairly fast. For me the best approach is to use testing packages for end packages. Things like wine, mplayer and games don't break much if they are broken. For those I use testing packages if they offer enough improvement. For core packages I allways go for stability.
Paul
-- [EMAIL PROTECTED] mailing list
