Neil Bothwick wrote: > On Tue, 5 Jan 2016 04:26:20 -0600, Dale wrote: > >> !!! The ebuild selected to satisfy >> ">=media-libs/mlt-0.9.8-r1[ffmpeg,kdenlive,melt,qt5,sdl,xml]" has >> unmet requirements. >> - media-libs/mlt-0.9.8-r2::gentoo USE="ffmpeg frei0r gtk kde kdenlive >> melt opengl python qt5 sdl xml -compressed-lumas -debug -fftw -jack >> -libav -libsamplerate -lua -qt4 -rtaudio (-ruby) -vdpau -xine" >> ABI_X86="64" CPU_FLAGS_X86="mmx sse sse2" PYTHON_TARGETS="python2_7" >> >> The following REQUIRED_USE flag constraints are unsatisfied: >> kde? ( qt4 ) > This says that if you have the kde flag enabled, you also need qt4. > >> The above constraints are a subset of the following complete >> expression: python? ( python_targets_python2_7 ) qt5? ( !qt4 ) kde? >> ( qt4 ) > This says you can't have qt5 and qt4 plus the above about kde. > > It looks like the qt5 and kde USE flags are incompatible. Try with > USE="-kde". > > Also, I have the -r2 ebuild in my portage tree but not -r1, so I suggest > you sync before trying anything else. > >
I sort of thought about it that way but it didn't make sense. How can I have KDE and not a kde USE flag was my thinking. After reading your post, I found out it likes the profile set to plasma, currently #8 on the list, instead of kde. Changing the profile got rid of this error and seems to have changed a few other things too. All I'm looking at now is a hard block on kde-apps/kde4-l10n-15.08.0-r1. I will sync again before actually starting the build. So, we have to change the profile setting to get to KDE5 as well. Interesting. Thanks. You got me closer. I'm doing all this in a separate file so that I can revert easily too. Since I have buildpkg set, it wouldn't take long to undo. Thanks much. Dale
