From owner-freebsd-ports@FreeBSD.ORG Tue Oct 16 09:18:12 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A996DCA for ; Tue, 16 Oct 2012 09:18:12 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id B5BCB8FC08 for ; Tue, 16 Oct 2012 09:18:11 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TO3Ht-000HzI-CW; Tue, 16 Oct 2012 11:18:09 +0200 Date: Tue, 16 Oct 2012 11:18:09 +0200 From: Kurt Jaeger To: Thomas Mueller Subject: Re: graphics/png status, when will 1.5.13 appear in ports? Message-ID: <20121016091809.GD12114@home.opsec.eu> References: <88.6C.17144.7542D705@smtp01.insight.synacor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88.6C.17144.7542D705@smtp01.insight.synacor.com> Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2012 09:18:12 -0000 Hi! > > > I didn't realize the FreeBSD ports people would be so cautious with png. > > > [5810 eitan@radar ~ ]%grep png-1.5 -c /usr/ports/INDEX-10 > > 6036 > > > might help explain why. :) > > > > Eitan Adler > > I don't have INDEX-10, but ran > grep png-1.5 -c /BETA1/usr/ports/INDEX-9 > and got 6032. > > Does that mean so many ports depend on png-1.5? Yes. > I guess they don't want to risk the small chance of png-1.5.13 breaking a > whole lot of ports? Yes, that's the reason. The ports tree has stability targets, freshness targets and time targets (like getting a RELEASE out), and probably some other targets as well. Sometimes, one target looses against one of the others. -- pi@opsec.eu +49 171 3101372 8 years to go !