From owner-freebsd-current@FreeBSD.ORG Sun Aug 31 23:58:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C2CE16A4BF; Sun, 31 Aug 2003 23:58:23 -0700 (PDT) Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C2843FA3; Sun, 31 Aug 2003 23:58:21 -0700 (PDT) (envelope-from kuku@accms33.physik.rwth-aachen.de) Received: (from kuku@localhost) by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h816wKd04306; Mon, 1 Sep 2003 08:58:20 +0200 Date: Mon, 1 Sep 2003 08:58:19 +0200 From: "Christoph P. Kukulies" To: Ruslan Ermilov Message-ID: <20030901065819.GB3811@gilberto.physik.rwth-aachen.de> References: <200308291454.h7TEsb913915@accms33.physik.rwth-aachen.de> <20030829172348.1aa0b5d4.Alexander@Leidinger.net> <20030829161907.GA89129@troutmask.apl.washington.edu> <20030830135427.0cea7fdb.Alexander@Leidinger.net> <20030830185653.GA10674@sunbay.com> <20030831140742.3bd1b597.Alexander@Leidinger.net> <20030831145224.GC28845@sunbay.com> <20030901051049.GB91933@dragon.nuxi.com> <20030901064424.GA30277@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030901064424.GA30277@sunbay.com> User-Agent: Mutt/1.4i cc: current@FreeBSD.org cc: Steve Kargl cc: Gordon Tetlow cc: Alexander Leidinger cc: Christoph Kukulies cc: David O'Brien Subject: Re: /lib symlinks problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 06:58:23 -0000 On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote: > I think that Gordon took a safe path with creating compatibility symlinks. > Besides, creating compatibility symlinks has a nicety of removing your > stale symlinks in /usr/lib. I always asked myself whether there is a tool or some kind of database at which one can throw an existing installation and it knows about which files have to be there and where and which ain't to be there (like such symlink relicts), maybe a hook in install,cp,ln and what else is being used in the world install process. That way it could tell me what files are candidates for deleting. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de