Date: Sat, 19 May 2007 16:21:49 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Michel Talon <talon@lpthe.jussieu.fr> Cc: Benjamin Lutz <mail@maxlor.com>, freebsd-ports@freebsd.org Subject: Re: Specs for saving old shared libs Message-ID: <464F868D.7020601@FreeBSD.org> In-Reply-To: <20070518140441.GA17685@lpthe.jussieu.fr> References: <20070518140441.GA17685@lpthe.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Michel Talon wrote:
> Not completely because some programs install shared libraries in very
> non standard places, notably perl installs perl.so like this:
> /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> or mozilla installs mozilla libs in another strange place. And there are
> other ports which make use of such shared libraries, for example Gnome
> depends on the mozilla libs or inn depends on perl.so.
That argument smells like a red herring to me. The (short version of
the) instructions I got from Pav:
1. Before deinstall, save shared libs in /usr/local/lib/compat/pkg
2. After install, remove anything from /usr/local/lib/compat/pkg with
the same name as something installed by the new port.
In the case of *.so (such as the mozilla or perl files in your
example) this would result in a noop. Can you suggest a case where
something useful would actually be preserved in lib/compat/pkg? And
assuming that you can, are you sure that these apps you're concerned
about will find what they are looking for in the ldconfig path,
instead of the location in the file system where they are looking for it?
I still feel that the only safe way to do this is to find the union of
'ldconfig -r' and 'pkg_info -L' and save those files, and those files
only.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?464F868D.7020601>