Hello James, Thursday, April 13, 2006, 2:06:40 PM, you wrote:
JC> Hugh McIntyre writes: JC> That's also what Debian does. That fixes the dependency problem, but JC> doesn't fix the path problem. JC> The path problem for libraries is that if one installs as JC> /opt/csw/lib/libfoo.so.1 JC> and the other installs as JC> /opt/sfw/lib/libfoo.so.1 JC> then one can't really satisfy the other. The user is forced straight JC> into LD_LIBRARY_PATH or crle(1) hell, and that's just not right. We do use Blastwave on our servers and I must say that I realy don't like all the problems with doubled libraries (like openssl). Sometimes you even endup linking with the library from blastwave while you were expecting something else - due to dependencies. Anyway I find blastwave really helpful. However I don't see what's wrong with having CCD - if someone wants to put his/her effort into Blastwave, CCD or Nexenta it's his/her choice. Competition is good - however some kind of base would be helpful so users could use different open source packages and mix them with minimal library mess, etc. -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
