Summary: | media-libs/jpeg-9 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Component: | New packages | Assignee: | Gentoo Graphics Project <graphics+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | kripton, siarhei.siamashka, vivo75 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.ijg.org/files/jpegsrc.v9.tar.gz | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lars Wendler (Polynomial-C) (RETIRED)
2013-01-14 10:43:04 UTC
+*jpeg-9 (14 Jan 2013) + + 14 Jan 2013; Samuli Suominen <ssuominen@gentoo.org> +jpeg-9.ebuild: + Version bump wrt #452008 by Lars Wendler. With empty KEYWORDS while waiting + for libjpeg-turbo to catch up. (In reply to comment #1) > +*jpeg-9 (14 Jan 2013) > + > + 14 Jan 2013; Samuli Suominen <ssuominen@gentoo.org> +jpeg-9.ebuild: > + Version bump wrt #452008 by Lars Wendler. With empty KEYWORDS while > waiting > + for libjpeg-turbo to catch up. https://sourceforge.net/p/libjpeg-turbo/feature-requests/18/ and also posted to their forums So it seems libjpeg-turbo upstream doesn't really want the new SmartScale feature from IJG's jpeg and even discredited the group with the backing of jpeg-6b author. It may be jpeg-9 never gets KEYWORDS. see also http://digikam.1695700.n4.nabble.com/libjpeg-8-requirement-considered-harmful-td4661294.html where red-hat and arch developers suggest >=libjpeg-8 NOT 9 is to be avoided. disclaimer, I'm just a messenger, not analyzed the situation of jpeg API and ABI in the various version. using libjpeg-turbo with jpeg8 abi enabled is safe, it just skips the smartscale that ijg's jpeg8 has we are certainly not falling back to jpeg6 without real need for doing so but i'm inclined to hold back jpeg9 for long as jpeg-turbo doesn't adapt to the latest smartscale features, and it propably doesnt Thanks Samuli, actually *after* commenting here I've read the libjpeg-turbo ebuild and realized it's using JPEG_ABI=8 , I've also commented on that thread with the resulting toughts. Should have looked at the ebuild sooner. |