[gentoo-user] Re: how thorough is #emerge --sync?

[Alexander Skwar <listen@alexander.skwar.name>]

Devon Miller <devon.c.miller@gmail.com>:

> You both seem to be arguing about what constitutes stable.

Yep. For emerge, all that matters is the tree. Nothing else is 
important - actually, nothing else exists, as overlays also become
part of the tree, sort of.

> And there are 2 
> different definitions: stable as defined by the upstream source and stable
> as defined in portage.

Yep. The latter is all that matters for emerge.

> Not appreciating the distinction, Maxim was asking why he's not getting the
> latest stable (expecting the "upstream stable").

We don't know what Maxim expected. Hence my question.

> Alexander's comments reflect the "portage stable",

Yes.

> but don't take in to 
> account that portage does not always keep up. 

As it doesn't matter to what emerge offers.

> In fact, in this case it's 
> languished rather badly.

Yes.

> His issue is 0.9.1 and 0.9.2 should have been stable by now.

I agree with this.

> 
> So, while Alexander is technically correct, (emerge is doing exactly what it
> should)

Yep. I asked, why maxim expected a different result.

> this not a good thing, because portage is still delivering older, 
> buggy code.

Yep.

> I would suggest Darren look through the develoiper list (
> http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml) for developers
> handling media-sound. Add them to the cc list on the 0.9.2 ebuild and add a
> comment asking that it be marked stable. And ask for the 0.9.3 to be added
> as ~x86

Very good suggestion!

Alexander Skwar
-- 
* BenC wonders why he has upgraded to 3.3.5-1 before teh X maintainer


-- 
gentoo-user@gentoo.org mailing list