| 1 |
Samuli Suominen posted on Mon, 23 Apr 2012 14:22:53 +0300 as excerpted: |
| 2 |
|
| 3 |
> Title: The default JPEG implementation |
| 4 |
|
| 5 |
[...] |
| 6 |
|
| 7 |
> All users are recommended to migrate: |
| 8 |
> |
| 9 |
> # emerge -C media-libs/jpeg:0 |
| 10 |
> # emerge -1 media-libs/libjpeg-turbo |
| 11 |
|
| 12 |
That of course leaves the system without a jpeg library between the jpeg |
| 13 |
unmerge and the completion of the libjpeg-turbo merge. If the build |
| 14 |
process fails for some reason... |
| 15 |
|
| 16 |
There's no way to use portage's automatic block-resolving ability here to |
| 17 |
avoid that, I take it? |
| 18 |
|
| 19 |
I'd suggest warning people that some image processing apps might not work |
| 20 |
during the interim, and possibly suggest using qpkg to package up the old |
| 21 |
version for quick binpkg remerge, if the build goes bad. And/or |
| 22 |
ebuild /path/to/libjpeg-turbo-ebuild package up the new version first, so |
| 23 |
it's know to have at least built and binpkged correctly, before unmerging |
| 24 |
jpeg. |
| 25 |
|
| 26 |
Since such instructions get a bit detailed for a news item overview, |
| 27 |
perhaps a link to a page explaining these sorts of details would be more |
| 28 |
appropriate than putting all that detail in the news item. |
| 29 |
|
| 30 |
> media-libs/jpeg:0 will be left in tree as a fallback implementation in |
| 31 |
> case libjpeg-turbo will become unmaintained or suffers from issues |
| 32 |
> caused by, for example, upgrading the toolchain. |
| 33 |
|
| 34 |
s/will become/becomes/ |
| 35 |
|
| 36 |
("Becomes" is more common usage and agrees better with "suffers" as well, |
| 37 |
which would otherwise need to be "will suffer" to match, but that's just |
| 38 |
a stilted construction all around, then.) |
| 39 |
|
| 40 |
Also possibly: s/in tree/in the tree/ |
| 41 |
Alternatively: s/in tree/in-tree/ |
| 42 |
|
| 43 |
("The" is arguably needed here, unless it's made a single compound word, |
| 44 |
in-tree. However, this isn't as odd sounding to me as the "in case ... |
| 45 |
will become" syntax and it may just be me being picky. Another opinion |
| 46 |
might be helpful.) |
| 47 |
|
| 48 |
Or better yet, the reasons the fallback might be needed don't really need |
| 49 |
to be enumerated at all. What about simply omitting that, leaving only: |
| 50 |
|
| 51 |
media-libs/jpeg:0 will be left in the tree as a fallback implementation. |
| 52 |
|
| 53 |
-- |
| 54 |
Duncan - List replies preferred. No HTML msgs. |
| 55 |
"Every nonfree program has a lord, a master -- |
| 56 |
and if you use the program, he is your master." Richard Stallman |
Archives