From owner-freebsd-questions@FreeBSD.ORG Mon Jul 19 06:40:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BAED16A4CE for ; Mon, 19 Jul 2004 06:40:51 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2833D43D55 for ; Mon, 19 Jul 2004 06:40:51 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i6J6eo9C020165; Mon, 19 Jul 2004 01:40:50 -0500 (CDT) (envelope-from dan) Date: Mon, 19 Jul 2004 01:40:50 -0500 From: Dan Nelson To: Travis Poppe Message-ID: <20040719064050.GD41912@dan.emsphone.com> References: <20040719002221.21b6b9a3@maya.liquidx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040719002221.21b6b9a3@maya.liquidx.org> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: Our package system: "Fundamentally Flawed" - A Linux User. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 06:40:51 -0000 In the last episode (Jul 19), Travis Poppe said: > Say for example I have a copy of gettext-0.13 on my system and one of > the binary packages I'm attempting to install was compiled and linked > against gettext-0.12? > > Instead of downloading and installing the other version of gettext > along with the existing one as to not break the linked libs (because > gettext-0.13 uses a different library name) like it should, pkg_add > only gives a warning and an assumption that the install went well. > > Now, the user goes to run the package and gets a big fat error: > libintl.so.X not found. > > For a user like myself, this is no problem. I can recognize the error > and figure out how to fix it manually. For a user considering > switching to FreeBSD from Linux, this is considered a "fundamental > flaw" in our package system and may lead to a very annoying flame > war. Can this be fixed? Why hasn't it been fixed? Am I doing > something wrong? Has it been fixed? Portupgrade should handle this correctly; when deleting old packages during an upgrade, it moves the shared libraries to compat/pkg so old binaries can still use them. If passed -PP, portupgrade will only use packages (with one -P, it will try and fetch a package but if it can't or the package is too old, it will build from source). Portupgrade is not in the base system because it requires Ruby, and scripting languages (apart from Bourne shell script :) change far too often to be in the base system. They're better off as ports so they can be updated more frequently. I'll let someone else answer your questions about frequency of port builds and why pkg_add doesn't fetch the latest ones. You can take a look at http://bento.freebsd.org and/or http://pointyhat.freebsd.org to see when the last full package buld was. -- Dan Nelson dnelson@allantgroup.com