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