On 01/19/2012 07:16 PM, "Paweł Hajdan, Jr." wrote:
On 1/19/12 6:02 PM, Samuli Suominen wrote:
On 01/19/2012 06:56 PM, Mike Frysinger wrote:
that doesn't help. the libjpeg turbo peeps themselves have said they
don't
guarantee compatibility across their own versions.
it's forward compatible, which is all we should care about
Just a note: that'd require me to DEPEND on a recent enough version of
libjpeg-turbo in the www-client/chromium ebuild, which would mean either:
a) changing the virtual/jpeg dependency to>=libjpeg-turbo-...
will be done soon as 1.2.0 is released and stabilized, i'd like to skip
1.1.90
and downgrading of libjpeg-turbo
I think this one should "just work", or at least not allow obvious
mistakes. See my a) b) c) notes above in this e-mail for possible
solutions and ideal SONAME.
a) is fine, preventing any downgrades. a fatal check, like glibc and
qt4 has to prevent downgrading is an option too, but a bit overkill imho
