On Thu, 22 Jan 2015 09:06:39 -0800 Zac Medico <zmed...@gentoo.org> wrote:
[...] > > That's what I understand from Michał's comment (quoting him): > > > >> 1. if you have dynamic-deps enabled, portage will want to install > >> both ffmpeg (because of :=) and libav (because of ||). The > >> effective deps will look like: > >> > >> || ( ffmpeg:0/51= libav ) ffmpeg:0/51= > > > > > > As I understand it, portage (correctly) marks this package for > > rebuild (because ffmpeg:0/51= dep isn't satisfied anymore), but I > > don't get why it doesn't consider the original '|| ( ffmpeg:= > > libav:= )' dep for the depgraph and wants to pull ffmpeg in > > "because of :=". > > It does consider the original dep. However, it also uses various > heuristics when making choices for || deps, and the fact that an > instance of ffmpeg is currently installed is taken into account in the > heuristics. good then; i'm assuming: people have ffmpeg installed and built a package 'foo' with || ( ffmpeg:= libav:= ); now, he removes ffmpeg, installs libav (put it in world), and masks ffmpeg (shouldnt be needed since it blocks libav but may hint portage solver). what Michał claims is that 'foo' will want ffmpeg, no matter what. how can it be possible if 'foo' is slatted for rebuild ? or maybe it is that portage does not slat it for rebuild (dynamic deps or not) ? how can it force to install ffmpeg then ? Alexis.
