cvs commit: src/lib/compat/compat4x.alpha libc.so.4.bz2.uu libc_r.so.4.bz2.uu libhistory.so.4.bz2.uu libm.so.2.bz2.uu libopie.so.2.bz2.uu libpcap.so.2.bz2.uu libperl.so.3.bz2.uu libreadline.so.4.bz2.uu

[David O'Brien]

On Sat, Oct 16, 2004 at 11:30:48AM +0900, Makoto Matsushita wrote:
> obrien> There is some debate about if compat libs should be placed in
> obrien> /usr/lib/compat or /usr/local/lib/compat.  I'm not sure what wa
> obrien> I fall on this... but I'd love to know if we have consensus among
> obrien> committers.
> 
> IMHO it depends on where compat libraries come from.  If it comes from
> a part of distribution, /usr/lib/compat is good, and if it comes from
> ports (or packages), ${LOCALDIR}/lib/compat would be better.
> 
> Since 6-current have no /usr/src/lib/compat, ${LOCALDIR}/lib/compat is
> enough for me.

Since the compat libs from a port can also be installed on 5.x do we
still want to not install them in /usr/lib/compat?  Also what about
machines that started out life as 5-CURRENT and are now 6-CURRENT?  They
will have compat libs in /usr/lib/compat that won't get cleaned up.
Since that location is searched before /usr/local/lib/compat people could
have a problem.


> Speaking about 'compat libs,' how do we supply older libraries that is
> in /lib?  Make a directory /lib/compat (or whereever in /), or ...?

I don't see why they should go in the / partition.  If you built a new
.so (say .so.1 -> .so.2), then you should also have all the /[s]bin
consumers of the .so lib updated [to use .so.2] also.  You could easily
have /usr/local/bin old binaries that still need the .so.1 version, but
they aren't part of boot on the / partition.  So they can get the compat
lib from /usr/lib/compat (or where ever compat libs are installed).
 
-- 
-- David  (obrien at FreeBSD.org)