On Thursday 13 April 2006 05:06 am, James Carlson wrote: > /opt/csw/lib/libfoo.so.1 > > and the other installs as > > /opt/sfw/lib/libfoo.so.1 > > then one can't really satisfy the other. The user is forced straight > into LD_LIBRARY_PATH or crle(1) hell, and that's just not right.
How can this happen. Presumably blastwave is compiling their own runpath into the binaries when they link, so how would these other libs even be used? I can't think of a reason that anyone should need to use LD_LIBRARY_PATH or crle which is the same kruft. > And it's not just libraries. Regular applications that are invoked by > scripts (would you like /opt/csw/bin/wget or /opt/sfw/bin/wget or > /usr/bin/wget to be found?) run into the path problem as well. This is a problem, where more than one binary exists. I had this happen on a friend's computer where he had the companion cd and blastwave installed, and my path was picking up sudo from /opt/sfw (which uses /opt/sfw/etc/sudoers), and he had his changes to the sudoers file in /opt/csw/etc/sudoers. Not only does this problem exist, I've experienced it first hand. > Not just "would be nice." I don't care about the disk space (I use > Blastwave regularly and enjoy it; the CCD bits are just too stale for > me). What I do care about is the library tragedy. Having two > separate libraries on the system that implement the same thing is > toxic to applications: you're just one dynamic link away from a > mystifying core dump. Providing the packages are compiled properly they should co-exist. Not saying it's not toxic to have multiple libs floating around, that's the very problem I would like to see solved.;-) > > (This is in part why you rarely ever find more than one libthing.so.N > library.) -- Alan DuBoff - Sun Microsystems Solaris x86 Engineering _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
