Looking for hints on getting kdewin-installer-gui-0.9.0-1.exe to work

[Ralf Habacker]

Gudmund Areskoug schrieb:
> Ralf Habacker wrote:
>   
>> Gudmund Areskoug schrieb:
>>     
>>>>> A Windows registry thing? Wonder if it's possible to do away with
>>>>> registry and/or forced installations, making things more like portable apps.
>>>>>       
>>>>>           
>>>> no
>>>>     
>>>>         
>>> Pity (if "no, we can't do away with registry etc." is what you meant).
>>>   
>>>       
>> i meaned the installer does not use any registry settings. You can move 
>> a kde installation to another path and should be able to run all 
>> applications from there (after a config update with kbuildsycoca4)
>>     
>
> Wonderful, will try. Perhaps I could bring a choice set of KDE apps
> along with me on my USB HD in the near future.
>   
yes, a msvc enduser installation needs about 350 MBytes, so it will fit 
also on a recent usb stick.

Just a few notes about usb hd/stick usage:

- Installing kde application on a usb stick or harddisc and accessing 
from a *different* drive letter on the *same* computer may result in 
partial data access problems, because some parts in the kde code stores 
the whole installation path in cache files (like the khelpcenter cache 
and kde icon cache). A workaround is to delete the 
.kde/cache-<computername> directory.

- the kde user data is located by the USERPROFILE environment variable 
(you can inspect them by running a console command -> dir 
"%USERPROFILE%"\.kde), you can override this by setting the KDEHOME 
environment variable say x:\.kde. All afterwards started kde application 
will use that directory for storing/retrieving user data.
> Next step after that would be to investigate how to "zwitter" it into
> being able to run things on Linux (maybe even Mac?) too. 
except the cache files as mentioned above. Because the cache directory 
contains the computername (cache-<computername>)  it can live side by 
side with caches created on unix/mac systems.
> The executables aren't cross-platform portable, presumably,
yes
>  but perhaps other things might be. 
yes
> At least the data repositories (mail files, documents etc.) and perhaps some settings files might/should be, 
The be menaingfull. There may be problem with different eol's. This have 
to be checked on an application base
> even if libraries probably aren't.
>   
yes.

Ralf