Owen Gunden <[EMAIL PROTECTED]> writes:

> emerge -u world *always* introduces potential for breakage.  emergers
> beware!

I think most of us are well aware of this, but it's certainly worth
pointing out again ;-)

> To me, the issue is that "emerge apache" should emerge the version of
> apache that gentoo recommends, not an old compatibility version.  

That's a good point, and I agree with it as a general rule. What I
have a problem with is that the definition of "apache" changes from
following one branch to another without any warning. 

> It looks to me that Gentoo is trying to understand the exact roles of and
> relationships between USE flags, package versions, and arch KEYWORDS.  It's
> going to take time, but hopefully when it's all figured out we'll have
> reached some nice intuitive definition which makes it very clear how to
> get the safety you're asking for.  Bear with the devs while this gets
> worked out.

If you're saying that this can all be sorted programmatically without
resorting to splitting up the portage tree then I'm all for
that. Although I trust myself to watch upgrades closely some kind of
sanity checking would be nice, even if it was just to flag up major
upgrades in a different colour or something.

-- 
Richard Watson
http://www.opencolo.com/
High Value Colocation

--
[EMAIL PROTECTED] mailing list

Reply via email to