On Fri, 14 Apr 2000, Kevin Atkinson wrote:
> > Try supporting this for 5000 users of your installed program across
> > 5000 workstations/PCs. This approach fails miserably.  Besides the
> > effort to get your users to use the same LD_LIBRARY_PATH, there is the
> > problem with conflicts between similarly named libraries.
> > 
> > The LD_LIBRARY_PATH variable was intended for developers, and it
> > should be treated as such.
> 
> What about supporting relocatable binaries with shared libraries in the
> same directory as the binary on some other path relative to the binary.
> This is found in many commercial programs.

Commercial programs typically include a shell script which sets
LD_LIBRARY_PATH (and other variables) in order to find the package
components.  While this may be fine for commercial software, it is not
acceptable for free software since free software must be held to a
higher standard of quality.

Bob
======================================
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen

Reply via email to