From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 22 22:38:15 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C657B106564A for ; Thu, 22 Apr 2010 22:38:15 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 93E0C8FC14 for ; Thu, 22 Apr 2010 22:38:15 +0000 (UTC) Received: by pwi9 with SMTP id 9so6622073pwi.13 for ; Thu, 22 Apr 2010 15:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JAV6DVCidDkDXBGsMrKGUTacwAJt34X8PyHX6N1Urwk=; b=MLvbuTETE3bM/69Vz7gF2S2igg+vAvvN/uq/t+U+Ns1tgVMrhemBRXRA6lLBcF170F pQCRYBSNJjG45dYl8mD303mHuurG54rvye5YMExY5r9eqLAQrzlV0YAF6L1A04upptnO Gjz6tGKUN7QGA6WgD3bKFzJKLzyz11zk3v6bc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hmyhbuyybF8F5VZR4l9e+/iabSg7nclm8bFT3jkm+zuVuAjk2oGw+MwFjvXCXyyz9s UdUSTWdVkqWJaHfo0/0VjrKU4UyYlTNN/F2Ly1W1Jz2xaz9v6phbe9zvq2LbbK8ObUzA c14Z2HlE91wFO5H5yC+WBCDySfqUKfAAL6SDs= MIME-Version: 1.0 Received: by 10.140.161.18 with HTTP; Thu, 22 Apr 2010 15:38:14 -0700 (PDT) In-Reply-To: <20100414174853.GC43908@dan.emsphone.com> References: <20100414174853.GC43908@dan.emsphone.com> Date: Thu, 22 Apr 2010 15:38:14 -0700 Received: by 10.141.108.19 with SMTP id k19mr4084899rvm.110.1271975894949; Thu, 22 Apr 2010 15:38:14 -0700 (PDT) Message-ID: From: Steve Franks To: Dan Nelson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Leinier Cruz Salfran Subject: Re: there is a way to avoid strict libraries linking? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2010 22:38:15 -0000 > It's much safer to just leave the libraries alone. =A0Just because you > upgraded libpng doesn't mean that your old gtk binary will stop working > (assuming you are using "portupgrade" or "portmaster -w" which preserves = old Untrue. Portupgrade deletes the old version of the port by default. The PNG upgrade was a major PITA, because I installed one new port that thought it had to have it. I'm sure 98% of the ports I then had to upgrade would have still worked just fine even if rebuilt against the old libpng. I think the complaint here is that the port dependencies system frequently gives the impression/enforces the rule that new ports will depend on whatever the most current version of everything is in the ports tree at the time they were built, forcing sort of a perpetual upgrade cycle. IMHO this is probably due to naive port maintainers (such as myself) incorrectly pointing a port at libpng.5 instead of any libpng, or libpng >=3D 5. Once the ports tree is 'poisoned' in this fashion, there's really no going back. I'd sure vote for an audit of this behavior as a summer of code project. Long story short, anything that sounds fundamental gets bumped (png, jpeg, tcl, python, gtk, etc, etc), I just sit back and get ready to spend two or three days retrying portupgrade -akOf -mBATCH=3Dyes until everything sticks. If you've got OO or KDE4 installed, you might just want to forget it and pkg_delete -f *, then start over. I'm sticking by bsd though. You don't even have the opportunity to run an automated tool to clean & build everything from source automatically on linux. I'm sure rpm & apt dependencies are even nastier. Steve