Date: Mon, 01 Sep 2003 01:22:49 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ru@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: /lib symlinks problem? Message-ID: <20030901.012249.118997606.imp@bsdimp.com> In-Reply-To: <20030901072017.GH30277@sunbay.com> References: <20030901064424.GA30277@sunbay.com> <20030901065819.GB3811@gilberto.physik.rwth-aachen.de> <20030901072017.GH30277@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030901072017.GH30277@sunbay.com>
Ruslan Ermilov <ru@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030901.012249.118997606.imp>