All systems have the exact same problem, Windows, Linux, and most
Unixes. Consider this:
Unix vendor ships version x.1.
Same vendor, different group ships a product, lets say C++. The C++
compiler depends on libc version x.1.1.
Vendor ships Unix version x.1.2 which includes libc version x.1.2.
Customer loads C++ which overrides libc x.1.2 and replaces it with the
older version x.1.1.
In the Linux space we solve this problem with RPM. (Or debian package
manager). The problem exists when you have products that need the
older libraries. In the Linux space we keep the libraries by version. In the
Windows space, not only do various installers load system DLLs but
some applications don't even ask. I find that the Windows dialog box is
confusing to users.
One of the things that MS should have done was to give DLLs versions
that could be easily checked during install. Anyhow, the various
Windows problems have helped Linux get a foot hold. Personally, I think
that there should be room for Windows, Linux and Unix, and Mac OS on
personal desktop systems.
On 31 Jan 00, at 15:29, Benjamin Scott wrote:
> > The same DLL hell can be encountered under Linux with shared libraries.
Jerry Feldman <[EMAIL PROTECTED]>
Associate Director
Boston Linux and Unix user group
http://www.blu.org
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
