From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 00:23:39 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 862D816A4BF; Mon, 1 Sep 2003 00:23:39 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4CF644001; Mon, 1 Sep 2003 00:23:38 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h817NbTX022629; Mon, 1 Sep 2003 01:23:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 01 Sep 2003 01:22:49 -0600 (MDT) Message-Id: <20030901.012249.118997606.imp@bsdimp.com> To: ru@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20030901072017.GH30277@sunbay.com> References: <20030901064424.GA30277@sunbay.com> <20030901065819.GB3811@gilberto.physik.rwth-aachen.de> <20030901072017.GH30277@sunbay.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: kuku@physik.rwth-aachen.de cc: current@FreeBSD.org 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 07:23:39 -0000 In message: <20030901072017.GH30277@sunbay.com> Ruslan Ermilov writes: : On Mon, Sep 01, 2003 at 08:58:19AM +0200, Christoph P. Kukulies wrote: : > 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. : > : Hold on, Warner is almost ready for an real solution here, I think. My tool is initially just a 'delete these files' tool, but now that I think about it, it wouldn't be hard to say also 'create these symlinks'. The hard part here is generating the 'obsolete' lists. Warner