On Thu, 23 Aug 2007 10:04:30 +0200, Abraham Marín Pérez wrote:
> > It is so, kino 1.1.0 pulls in ffmpeg-0.4.9_p20070616, which doesn't
> > cause any blocks. The facts that the block disappears when you switch
> > to 1.1.0 should be enough to convince you.
> The block isn't caused by ffmpeg, but by kino's ebuild.Which contains those lines because Kino 1.0.0. doesn't work with later versions of ffmpeg. The ebuild is responding to the situation, not causing it. > Kino 1.1.0 is > still marked as unstable, and I guess devs have a good reason to do > such a thing. See my other post for the workaround. Yes, the reason is that policy is that ebuilds should remain in testing for around thirty days. This doesn't mean the software is unstable or unfit for use, only that the ebuild had not received sufficient testing to meet the criteria for inclusion i the stable tree. -- Neil Bothwick The fact that no one understands you doesn't mean you're an artist.
signature.asc
Description: PGP signature
