From owner-freebsd-ports@FreeBSD.ORG Sat Feb 6 04:24:49 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 091E3106566B for ; Sat, 6 Feb 2010 04:24:49 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8210E8FC08 for ; Sat, 6 Feb 2010 04:24:48 +0000 (UTC) Received: by wwj40 with SMTP id 40so783395wwj.13 for ; Fri, 05 Feb 2010 20:24:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=CCnbIFljp1+QVABvUQ0S0BBhXvbLDh2EvYILP/oVZPs=; b=nzRtyigvk0NmfS3YDXpVgqkf7BcoRGcRxp2o8Qvfwgn6CtKcFvBDvt3KAjnPWqw03t mRBWkuNlPinD3EnimwCfm0qRu8QR2kPEOPY+zi6c/gjBuqQMcdmjaGXXVrAjl4KIFY7l VAUaxGwnQBM3eh+EwHPI9PsvN5MTQT39vD0ZM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SkTZs8w2C+VIfFrW8WqcfaZixBrcbEPHX96oZgipB3tGQWB+3DEv9m8ASUz8t+uicY KBHDqCv3E2WfYwZVqsUs4zO1YbeM0jl6YL5/ieFQj0uWhOwns+mIRxUzN1mPJY6N9l5h CRqaOVWiFvkZZolbKAjSBZSPlsV8i5BIuNfuM= MIME-Version: 1.0 Received: by 10.216.88.71 with SMTP id z49mr1997775wee.90.1265430287598; Fri, 05 Feb 2010 20:24:47 -0800 (PST) Date: Fri, 5 Feb 2010 23:24:47 -0500 Message-ID: From: "b. f." To: freebsd-ports@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: Recent massive port update. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2010 04:24:49 -0000 jhell wrote: >I could have swore that I recently heard an announcement that barred this >type of activity until after 7.3-RELEASE was made.... > >Guess that doesn't stand for everything. That freeze won't start until around Feb. 8, as announced. The jpeg changes were announced earlier by the maintainer on this list on Jan. 24: http://lists.freebsd.org/pipermail/freebsd-ports/2010-January/059129.html >Was there some type of security concern that caused this bump of jpeg in >the first place or was it just a creeping featurism? The Independent JPEG group has always announced that they are going to incorporate changes and improvements into their software, and that it is not fixed in stone. The pace of change has varied. Your tone suggests that you meant "creeping" in a pejorative sense: if you don't like the changes, you can stick with the old version, or write your own software.