On Mon, Feb 10, 2003 at 08:58:56PM +0100, Ingo Krabbe wrote:
> This sounds to me exactly as the error means:
> gnome2.2 is stable but some of the dependancies aren't so if you want to
> update to gnome2.2 you have either to accept beta packages or stream
> down the gnome2.2 if you can mask out one or some other package from the
> dependancy list.
> 
> Since gnome2.2 should be some kind of virtual package it shouldn't be
> stable until all of its dependancies are. So this also could be
> understood as an error.
> 
> BUT ! The dependancies might vary by change of use flags.  So gnome2.2
> could be called stable once all possible use variations that effect its
> dependancy tree will also mask completly stable.
> 
> This sounds like a hard rule for a real intelligent software.
> 
> At least it turns out that YOU are the most intelligent part in that
> process, so you have to tune on that error, not your software.  I fear
> that you have to accept that gnome2.2 isn't stable for you yet, so you
> should mask itself out with ~x86 (in you personal portage tree) or
> accept beta packages at least to emerge -u gnome.
> 
> But that's only my opinion: I would vote against calling this an error
> actually.

Yes, I came the the same conclusions.  It just seems strange that all
packages are not set to stable when the main meta package (gnome) is.
Normally things that cause those sorts of problems stay away from
stable. 

-- 
Alan <alan@...> - http://arcterex.net
---------------------------------------------------------------------
"The only thing that experience teaches us is that experience teaches 
us nothing.	        -- Andre Maurois (Emile Herzog)

--
gentoo-dev@g.o mailing list