Peter Tribble wrote:
That's not at all reasonable. I certainly don't want applications or libraries that I may need to install my own versions of in the standard system locations. Doing so only makes the possibility of conflict more likely. Shoving things like openssl away in /usr/sfw is nice and safe - it gives you the option of using them (if you wish) or ignoring them completely (if you wish).
What exactly is it about OpenSSL that makes it so special for you that you need to do this ? Why can't you as the person building the local software that needs its own local version use your local copy ? Proper use of ld(1) and ld.so.1(1) flags,config files and environment already allow this. Why doesn't this apply for other things /usr/lib or /lib ? Do you do this on other platforms as well ? IIRC RedHat and SuSE both ship OpenSSL's libssl and libcrypto in /usr/lib. So how is this "problem" dealt with on systems like that ? On the flip side of this having OpenSSL in /usr/sfw has lead a lot of people to think that we don't ship it or don't support it. The "hiding" in /usr/sfw was never a good idea and we all know that now. -- Darren J Moffat _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
