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