Message-ID: <4A475435.1060505@gmail.com>
Date: Sun, 28 Jun 2009 12:29:57 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [RFC] jpeg library
References: <4A466538.8030007@cwilson.fastmail.fm> <4A46FAA4.2@users.sourceforge.net> <4A470ADF.5010306@cwilson.fastmail.fm> <4A471802.5030001@users.sourceforge.net>
In-Reply-To: <4A471802.5030001@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Yaakov (Cygwin/X) wrote:
> On 28/06/2009 01:17, Charles Wilson wrote:
>> Nope. Upstream development is DEAD.  There was some flurry of activity
>> about two years ago, but it never went anywhere.   If IJG's libjpeg
>> wasn't so widespread and widely used, I'd want to look at some other
>> library that supports the format...
> 
> Actually, are you sure about that?  http://www.ijg.org/ lists a version
> 7, released yesterday, as the current version.

  I was just about to say "We could always try and find a security
vulnerability, that's the only thing that would cause upstream to update
libjpeg these days!  :)  But then I took a look at the new change.log and it's
actually crammed with new and improved functionality, so this is an ideal
opportunity.

  I think the makes freezing (obsoleting) libjpeg-6b forever with the lossless
patch incorporated, and just moving to a straight unpatched release of
libjpeg-7 a no-brainer doesn't it?  What a fortuitous bit of timing!

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple