1 |
On 04/23/2012 10:49 AM, Pacho Ramos wrote: |
2 |
> El lun, 23-04-2012 a las 10:17 -0400, Mike Gilbert escribió: |
3 |
>> On Mon, Apr 23, 2012 at 8:28 AM, Duncan<1i5t5.duncan@×××.net> wrote: |
4 |
>>> Samuli Suominen posted on Mon, 23 Apr 2012 14:22:53 +0300 as excerpted: |
5 |
>>> |
6 |
>>>> Title: The default JPEG implementation |
7 |
>>> |
8 |
>>> [...] |
9 |
>>> |
10 |
>>>> All users are recommended to migrate: |
11 |
>>>> |
12 |
>>>> # emerge -C media-libs/jpeg:0 |
13 |
>>>> # emerge -1 media-libs/libjpeg-turbo |
14 |
>>> |
15 |
>>> That of course leaves the system without a jpeg library between the jpeg |
16 |
>>> unmerge and the completion of the libjpeg-turbo merge. If the build |
17 |
>>> process fails for some reason... |
18 |
>>> |
19 |
>>> There's no way to use portage's automatic block-resolving ability here to |
20 |
>>> avoid that, I take it? |
21 |
>>> |
22 |
>> |
23 |
>> This works for me. |
24 |
>> |
25 |
>> floppym@naomi ~ % emerge -pv1 -j1 libjpeg-turbo |
26 |
>> |
27 |
>> These are the packages that would be merged, in order: |
28 |
>> |
29 |
>> Calculating dependencies... done! |
30 |
>> [ebuild N ] media-libs/libjpeg-turbo-1.2.0-r1 USE="-java |
31 |
>> -static-libs" 0 kB |
32 |
>> [uninstall ] media-libs/jpeg-8d USE="-static-libs" |
33 |
>> [blocks b ] media-libs/jpeg:0 ("media-libs/jpeg:0" is blocking |
34 |
>> media-libs/libjpeg-turbo-1.2.0-r1) |
35 |
>> |
36 |
>> |
37 |
> |
38 |
> I guess it will work when jpeg is not in world file... maybe people |
39 |
> should be told to drop it and, then, let emerge do all the work |
40 |
> automatically. |
41 |
|
42 |
This will do the trick: |
43 |
|
44 |
emerge --deselect media-libs/jpeg |
45 |
emerge --oneshot media-libs/libjpeg-turbo |
46 |
|
47 |
-- |
48 |
Thanks, |
49 |
Zac |