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