matthew green wrote:

>    Log Message:
>    Now that install has been fixed to deal with -r in the symlink case,
>    make bsd.lib.mk use INSTALL_SYMLINK instead of mv and ln -s.
>    Note: There is still one weird case I left alone, in which symlinks
>    get built in the objdir. I didn't want to log metadata for those links
>    so I left the old machinery in for them.
>    XXX do we even need that elaborate dance for the ln's in the objdir?
> 
> is this for shlibs?  yes please.  i want to be able to continue to
> set LD_LIBRARY_PATH=/usr/src/lib/libc/obj.foo and get my new shlibs
> before they're installed....

I _think_ Perry means that the

	ln -sf lib${LIB}.so.${SHLIB_FULLVERSION} lib${LIB}.so.${SHLIB_MAJOR}.tmp
	mv -f lib${LIB}.so.${SHLIB_MAJOR}.tmp lib${LIB}.so.${SHLIB_MAJOR}
	ln -sf lib${LIB}.so.${SHLIB_FULLVERSION} lib${LIB}.so.tmp
	mv -f lib${LIB}.so.tmp lib${LIB}.so

can just be

	ln -sf lib${LIB}.so.${SHLIB_FULLVERSION} lib${LIB}.so.${SHLIB_MAJOR}
	ln -sf lib${LIB}.so.${SHLIB_FULLVERSION} lib${LIB}.so

(ie, without the "install to .tmp and rename" dance).

Now, if you do

	env LD_LIBRARY_PATH=/usr/src/lib/libc/obj.foo exec <yourshell>

it could be argued that maybe you should lose every now and then :-)

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD CDs, Support and Service:    http://www.wasabisystems.com/