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