Actually, I agree with the thought of using a separate directory for the libraries, but it should only be necessary when the need library cannot be found on the system that you are loading on. You are probably correct in the cause of dll-hell, however if the libraries were more standardized it might help as well. Jonathan
-----Original Message----- From: Nick LeRoy [mailto:nleroy@cs.wisc.edu] Sent: Tuesday, June 10, 2003 1:21 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Microsoft Vs. Linux Desktop Battle Heats Up
If the package would include the necessary libraries to install and run, rather than being dependentant on what the distro may already come with, should resolve this issue. For the most part just about every package I have come across I could compile and execute on Mandrake, SuSE, Red Hat, Debian, and *BSD. There is only the matter of porting the
On Tuesday 10 June 2003 1:03 pm, Jonathan Shilling wrote: libraries.
Jonathan
Sorry, but I ardently disagree here. This is what all the Windoze apps do, and is IMHO what's been known to cause the DLL-hell that anybody whose ever used windoze has battled too many times.
Now, I suppose I might relax my position _if_ it could install these libs in a non-shared (ie app specific) location. Instead of installing a different libfoo.so in /usr/lib, package bar installed in, say, /opt/bar, and installed /opt/bar/lib/libfoo.so and /opt/bar/bin/bar is a shell script that sets LD_LIBRARY_PATH before starting the _real_ /opt/bar/bin/bar.bin. Even then, however, I'd say this should only be done _when neccessary_.
-Nick
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com