>> What might cause the application to not work properly? > >Compiled-in paths. If an application expects to find its files at location >X, then you're out of luck putting them at /someplace/Y/.
But if I use a symlink from location X to location /someplace/Y/, then the application should still find the file that is in /someplace/Y/, even though it thinks it is looking in location X. I can't see that this is a problem? >making them relocatable. Often there's no big need to do it. Except user flexibility ... >I don't believe you. E.g. I want this (*^@#&* piece not to dump its dlls >into c:\windows\. I bet I'm out of luck. Never mind, who cares on this >list about that. dlls are often shared files, just like glib etc. Obviously these types of files need to be located in a known common location. Application specific stuff still ends up in a directory of it's own. >> I just want to be able to do the same. > >Why? > >If you expect your linux system to always exactly behave like your M$ >one, use M$. You'll be happier to go with things as they are, rather >than forcing them into the only thing you're used to. I don't expect to have linux behave like M$ - that's why I use it! At least I can still run a decent OS on my old slow machine at home, with small HDs. That's "WHY" I want to be able to install in a different location - because I have to manage my limited space... Paul.
