The ebuilds of Chromium > 18.0.1025 should not force the use of libjpeg-turbo (>=media-libs/libjpeg-turbo-1.2.0-r1) but rather use the virtual/jpeg and depending on what jpeg lib is used to set or unset the Chromuim 'use_libjpeg_turbo' flag ATM, Chromium ebuild forces the use of libjpeg-turbo thus conflicting with the native media-libs/jpeg:0 and requiring it to be removed. This behaviour is bad. Please fix for the next versions. Reproducible: Always
(In reply to comment #0) > The ebuilds of Chromium > 18.0.1025 should not force the use of > libjpeg-turbo (>=media-libs/libjpeg-turbo-1.2.0-r1) but rather use the > virtual/jpeg and depending on what jpeg lib is used to set or unset the > Chromuim 'use_libjpeg_turbo' flag There was a reason for doing this wrt bug 393471. This seems like a duplicate of it. > ATM, Chromium ebuild forces the use of libjpeg-turbo thus conflicting with > the native media-libs/jpeg:0 and requiring it to be removed. This behaviour > is bad. Why do you think it's bad? The IJG's media-libs/jpeg:0 is considered more or less deprecated in favour of libjpeg-turbo. We are in process of getting libjpeg-turbo stabilized on all arch's and dropping KEYWORDS from it. *** This bug has been marked as a duplicate of bug 393471 ***
(In reply to comment #1) > We are in process of getting libjpeg-turbo stabilized on all arch's and > dropping KEYWORDS from it. to clarify, "from it" -> "from media-libs/jpeg:0" > *** This bug has been marked as a duplicate of bug 393471 ***
LOL an amazing answer.... Considered more or less deprecated??!? By whom??? IJG's joeg is still the standard for all Lin distroes!!!... And btw jpeg turbo has a lot of issues... You should not replace a stable system lib just because of one package - chromium... And then where is the choice of the user (if to use the orig jpeg lib or some 'optimised' clone)??? Or we shall make everything working like in Windows - forced?... Actually if you implement this change later in stable versions... you may remove the virtual/jpeg because of its uselessness :P And btw i do not think this bug is at all a duplicate of bug 393471 Anyway this is not a forum ... I just stated my opinion about an issue and pointed you to a link upstream that discusses the matter... Your choice if you will fix it or not(obviously you will not even consider it... you just closed it as duplicate :D ). I've already done it in my local overlay... Once again an amazing Gentoo QA standards :D
(In reply to comment #3) > LOL an amazing answer.... > > Considered more or less deprecated??!? By whom??? IJG's joeg is still the > standard for all Lin distroes!!!... You are wrong, https://fedoraproject.org/wiki/Features/libjpeg-turbo http://www.archlinux.org/packages/extra/i686/libjpeg-turbo/ (Provides: libjpeg=8.0.2) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034 https://launchpad.net/ubuntu/+source/libjpeg-turbo/ Nearly every major distribution is in process of switching or considering switching. virtual/jpeg is for migration *to* libjpeg-turbo and without valid response this is a duplicate of said bug.
