Hi. Some people are having troubles when try to update their system because of unmasked versions of ffmpeg. They need to unmask ffmpeg to use chromium, because depends on a masked version of ffmpeg (media-video/ffmpeg-0.5-_p19928) But now, the stable version of ffmpeg is media-video/ffmpeg-0.5-r1 , and chromium compiles perfect with that version, and workd perfect too. So, I have changed the chromium ebuild to fix that dependence issue. And I have tried to emerge chromium using the stable version of ffmpeg. # qlist -I -v -e media-video/ffmpeg media-video/ffmpeg-0.5-r1 # grep 'media-video/ffmpeg' /usr/portage/www-client/chromium/chromium-4.0.248.0.ebuild >=media-video/ffmpeg-0.5-r1 This is the interesting part of emerge.log: 1258574340: Started emerge on: Nov 18, 2009 20:59:00 1258574340: *** emerge --ask www-client/chromium 1258574369: >>> emerge (1 of 1) www-client/chromium-4.0.248.0 to / 1258574385: === (1 of 1) Cleaning (www-client/chromium-4.0.248.0::/usr/portage/www-client/chromium/chromium-4.0.248.0.ebuild) 1258574385: === (1 of 1) Compiling/Merging (www-client/chromium-4.0.248.0::/usr/portage/www-client/chromium/chromium-4.0.248.0.ebuild) 1258579861: === (1 of 1) Merging (www-client/chromium-4.0.248.0::/usr/portage/www-client/chromium/chromium-4.0.248.0.ebuild) 1258579866: >>> AUTOCLEAN: www-client/chromium:0 1258579877: === (1 of 1) Updating world file (www-client/chromium-4.0.248.0) 1258579877: === (1 of 1) Post-Build Cleaning (www-client/chromium-4.0.248.0::/usr/portage/www-client/chromium/chromium-4.0.248.0.ebuild) 1258579877: ::: completed emerge (1 of 1) www-client/chromium-4.0.248.0 to / 1258579877: *** Finished. Cleaning up... 1258579877: *** exiting successfully. 1258579880: *** terminating. Ok, and now I'm using the new installed chromium to submit this bug. Please, could be possible to change the chromium ebuild to fix that dependence issue? Thank you in advance. Reproducible: Always
You mean on stable systems? Yes indeed, mixing stable and unstable can sometimes leads to headaches... ffmepg is only used for HTML5 <video> tags, and it requires a new enough ffmpeg (0.5 is too old). The libraries are checked at runtime, so in fact you should even be able to merge chromium without any ffmpeg around. What I can do is make this dependency optional (USE-flag), so you don't have to run through the ffmpeg upgrade (yet) just to run the browser. Renaming bug accordingly
Yes, I use stable. My accept_keywords is amd64 , NOT ~amd64. It's a very good idea to have a USE flag for that, thank you!
Done in -4.0.251.0 and -9999, ffmpeg USE-flag now controls if you want to have HTML5 audio/video tags support (so setting -ffmpeg in package.use for stable will not depend on unstable ffmpeg) Thanks for the report!
