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 03:37:25PM +0900, Makoto Matsushita wrote:
> Maybe it's ok with /{s,}bin and other binaries those come from ports,
> but how about user-made custom binaries for their system backups or
> host administration related tools?  They also live somewhere in /.
> 
> As we can easily comes "Since they also have a source, just recompile
> them all" solution, but I'm afraid that that's not ok...

If these user-made custom binaries were installed in /[s]bin, I think we
can assume the user/sysadmin is capable of coping any needed .so's from
/usr/lib/compat to /lib.  In fact, this custom binary may easily had a
.so usage for a lib we have in /usr/lib vs. /lib because none of the
stock /[s]bin binaries need it.  So the user/sysadmin has already had to
deal with the issue by hand.

-- 
-- David  (obrien at FreeBSD.org)