From owner-freebsd-ports@FreeBSD.ORG Tue Jun 19 17:23:47 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 885F6106566B; Tue, 19 Jun 2012 17:23:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id EA22E8FC1A; Tue, 19 Jun 2012 17:23:46 +0000 (UTC) Received: by werg1 with SMTP id g1so5864396wer.13 for ; Tue, 19 Jun 2012 10:23:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NyG9GwyB3bdryP5jz2jQaFD1eJ6aO1h9sTsV6TR5H+I=; b=FN9PXRkae4oPkOUb0/UT0PwOJaZRNyPXuOY5oKq3hnomiMPdplhs/5s1edrW2Vz3+r Ulcqf/RyC9fb28m3UteU7qQt5+dD9m47/LES0yTCbViGtuBteXC7c2MRAwYhlQXAZulY 3RWUsOpBuLhrsJmhdOIQUO0oDxo7RAMhB+glxCMEKqUbG5TDSFFoSNlKlHtXW7nbjrW7 Xq9dG47wkcKmbr7FiHJcSNEmGWJBGhxz5qn2yZotd4MUlpG4LX9XHfbALcpA4/Co7lYq rBAkzEBIuREXSJ672EKrvEoPh8bnAfEPxYElLoDftXcphyQdVOOy/iGgGNsqLFt0vnfW 6d7Q== MIME-Version: 1.0 Received: by 10.216.215.194 with SMTP id e44mr11719270wep.61.1340126625883; Tue, 19 Jun 2012 10:23:45 -0700 (PDT) Received: by 10.223.155.4 with HTTP; Tue, 19 Jun 2012 10:23:45 -0700 (PDT) In-Reply-To: <3E.40.07469.5A440EF4@smtp02.insight.synacor.com> References: <3E.40.07469.5A440EF4@smtp02.insight.synacor.com> Date: Tue, 19 Jun 2012 10:23:45 -0700 Message-ID: From: Kevin Oberman To: Thomas Mueller Content-Type: text/plain; charset=UTF-8 Cc: dinoex@freebsd.org, freebsd-ports@freebsd.org Subject: Re: png-1.5.11 status? 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: Tue, 19 Jun 2012 17:23:47 -0000 On Tue, Jun 19, 2012 at 2:21 AM, Thomas Mueller wrote: > What is the current status of newly-released png-1.5.11? > > My main concern is having to portupgrade/portmaster all ports that have png as a dependency, > don't want to have to do this for png-1.5.10 and then a day or two later for png-1.5.11. > > Maybe NetBSD pkgsrc promptly updated png to 1.5.11 because they wanted to get it in before the freeze for pkgsrc-2012Q2? Unless the shareable version number is bumped, there is no need to re-build dependent ports. Most updates to shareables do not change the API or ABI, so dependent packages simply pull in the updated shareable when they load. You should only have to do the mass update once, whether for 1.5.10 or 1.5.11. I would suggest using the '-w' option if you use portmaster as the old shareable was libpng and the new is libpng15. If you keep a copy of the old one around, many things that have not been re-linked will still run OK. Note that when you start re-building stuff, you will certainly hit cases when you link to a library linked to one libpng and either the port being installed or another dependency is linked to libpng15. I'm unsure exactly what impact that might have. It really should have none, but I am not really sure. When you are finished re-building (or think that you are), I strongly recommend running "pkg_libchk -o | grep png" to make sure that nothing has been missed. pkg_libchk is part of the sysutils/bsdadminscripts port. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com