| 1 |
On Mon, Apr 23, 2012 at 8:28 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
| 2 |
> Samuli Suominen posted on Mon, 23 Apr 2012 14:22:53 +0300 as excerpted: |
| 3 |
> |
| 4 |
>> Title: The default JPEG implementation |
| 5 |
> |
| 6 |
> [...] |
| 7 |
> |
| 8 |
>> All users are recommended to migrate: |
| 9 |
>> |
| 10 |
>> # emerge -C media-libs/jpeg:0 |
| 11 |
>> # emerge -1 media-libs/libjpeg-turbo |
| 12 |
> |
| 13 |
> That of course leaves the system without a jpeg library between the jpeg |
| 14 |
> unmerge and the completion of the libjpeg-turbo merge. If the build |
| 15 |
> process fails for some reason... |
| 16 |
> |
| 17 |
> There's no way to use portage's automatic block-resolving ability here to |
| 18 |
> avoid that, I take it? |
| 19 |
> |
| 20 |
|
| 21 |
This works for me. |
| 22 |
|
| 23 |
floppym@naomi ~ % emerge -pv1 -j1 libjpeg-turbo |
| 24 |
|
| 25 |
These are the packages that would be merged, in order: |
| 26 |
|
| 27 |
Calculating dependencies... done! |
| 28 |
[ebuild N ] media-libs/libjpeg-turbo-1.2.0-r1 USE="-java |
| 29 |
-static-libs" 0 kB |
| 30 |
[uninstall ] media-libs/jpeg-8d USE="-static-libs" |
| 31 |
[blocks b ] media-libs/jpeg:0 ("media-libs/jpeg:0" is blocking |
| 32 |
media-libs/libjpeg-turbo-1.2.0-r1) |
Archives