| 1 |
On 04/23/2012 01:43 PM, Ulrich Mueller wrote: |
| 2 |
>>>>>> On Mon, 23 Apr 2012, Samuli Suominen wrote: |
| 3 |
> |
| 4 |
>> I don't really think this is necessary, but some people seem to. |
| 5 |
>> Looks fine? |
| 6 |
> |
| 7 |
>> Title: The default JPEG implementation is libjpeg-turbo |
| 8 |
> |
| 9 |
> Too long. GLEP 42 allows a maximum of 44 characters only. |
| 10 |
> |
| 11 |
>> Author: Samuli Suominen<ssuominen@g.o> |
| 12 |
>> Content-Type: text/plain |
| 13 |
>> Posted: 2012-04-23 |
| 14 |
>> Revision: 1 |
| 15 |
>> News-Item-Format: 1.0 |
| 16 |
>> Display-If-Installed: =media-libs/jpeg-8* |
| 17 |
> |
| 18 |
>> libjpeg-turbo is a derivative of libjpeg that uses MMX, SSE, SSE2, and NEON |
| 19 |
>> SIMD instructions to accelerate baseline JPEG compression/decompression by |
| 20 |
>> about 2-4x on x86, x86-64, and ARM platforms. It is based on libjpeg/SIMD but |
| 21 |
>> has numerous enhancements. |
| 22 |
> |
| 23 |
> I'd suggest to use our standard names for these architectures, i.e. x86, |
| 24 |
> amd64, and arm. |
| 25 |
> |
| 26 |
>> All users are recommended to migrate: |
| 27 |
> |
| 28 |
>> # emerge -C media-libs/jpeg:0 |
| 29 |
>> # emerge -1 media-libs/libjpeg-turbo |
| 30 |
> |
| 31 |
>> > From here on out media-libs/jpeg:0 is only used as a fallback and at the time |
| 32 |
>> of writing this news item, libjpeg-turbo has no known bugs that would require |
| 33 |
>> using it. |
| 34 |
> |
| 35 |
> Maybe avoid the word "From" at the beginning of the line. eselect news |
| 36 |
> will escape it properly, but it looks somewhat ugly. |
| 37 |
> |
| 38 |
> And please wrap the body text at 72 chars (GLEP 42 says so). |
| 39 |
|
| 40 |
Thanks Ulrich. See attachment as draft #2. |
Archives