From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay1.mentorg.com ([192.94.38.131]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1P3qo0-0007Y6-O4 for openembedded-devel@lists.openembedded.org; Thu, 07 Oct 2010 15:46:46 +0200 Received: from svr-orw-exc-08.mgc.mentorg.com ([147.34.98.97]) by relay1.mentorg.com with esmtp id 1P3qne-0006cx-Fm from Tom_Rini@mentor.com for openembedded-devel@lists.openembedded.org; Thu, 07 Oct 2010 06:46:22 -0700 Received: from na2-mail.mgc.mentorg.com ([134.86.114.213]) by SVR-ORW-EXC-08.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Oct 2010 06:46:22 -0700 Received: from [172.30.80.69] ([172.30.80.69]) by na2-mail.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 7 Oct 2010 07:46:20 -0600 Message-ID: <4CADCF1E.3090602@mentor.com> Date: Thu, 07 Oct 2010 06:46:06 -0700 From: Tom Rini Organization: Mentor Graphics Corporation User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org X-OriginalArrivalTime: 07 Oct 2010 13:46:20.0785 (UTC) FILETIME=[0621A610:01CB6626] X-SA-Exim-Connect-IP: 192.94.38.131 X-SA-Exim-Mail-From: Tom_Rini@mentor.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Updating libtiff X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2010 13:46:46 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hey all, I'm looking to update libtiff to cover some security issues in the version we ship, and I noticed something funny about how we do it today. Currently tiff_3.9.2.bb sets PV to 3.9.2+4.0.0beta5 and grabs and builds 4.0.0beta5. While it's possible that in the past 3.9.2 was intended to be the last 3.9.x, it wasn't. I think we should go with: - Add tiff_4.0.0beta6.bb which should be compatible with beta5 and will get upgrades right. - Add tiff_3.9.4.bb as well, in case someone wants to stay on the released line. Anyone see a problem with that? -- Tom Rini Mentor Graphics Corporation