[gentoo-amd64] Re: Re: Gnome 2.12... to 2.14... on X11 v7!

[Duncan]

"Christopher E" <sensory.access@×××××.com> posted
184c54640605110628x5cfdf346wa98eb487bd20aac9@××××××××××.com, excerpted
below, on  Thu, 11 May 2006 09:28:22 -0400:

> OK, seeing that this seemsto be a workable setup, which order would
> you do this in.
>
> I notice that the new verion of gnome pulls in things of x11 but I
> don't know if this is for the newer X11 or a older X11.

In general, it doesn't much matter.  Portage's dependency tracking sorts
it all out for you.  Of course, that depends on the dependencies in the
ebuild being correct -- occasionally they aren't -- but a bad dependency
is a bug and should be processed as such, not the normal behavior.

Here, I do an emerge --sync and then an emerge --newuse --update --deep
(with the requisite --pretend to see what it's going to do first) several
times a week, so everything is routinely updated, and when a new version
of whatever comes out, it doesn't force updating of much else, because 
everything else was already updated when its update first came out.  The
--deep is the critical parameter there, as it tells portage to update not
just the stuff in the world file, but all dependencies thereof, as well. 
Since I do it nearly daily, there's never a big backlog of packages to
merge, since I'm always caught up.  The exception is things like a new
kde release, where all the kde-base packages get updated at once and
there's typically over a hundred individual packages to update.  However,
that's just the way a kde release works, and at least I don't have much
/else/ to update then because everything else is upto date already.



-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list