Installing MS Office gives error in installer

[Speeddymon]

> I dont think you should go by asking the user. You> cant be sure, if he knows > it right. The question is not only about its kde> version, but also the > directory of his config files...which config files would you be referring to?> > Besides, this script is not intended to ask for user> input.> > You will be better of, if you just fix my patch, to> not copy to .kde by > default, but check if there exists a .kde2 and in> that case to copy there.> Actually I decided not to ask for the user input after all, instead it runs kded -v (if kded exists since i wasn't sure if kde 1.x had it or not) and greps the output for KDE: and sed's that to remove the KDE: (so that just the version number is there) and then writes that to /tmp/kdeverif /tmp/kdever doesn't exist then it proceeds like it would have before my patchif it does, it sed's the number in there for the first part of that number (1 or 2) and uses that to determine if you are running kde1 or kde2if you are running kde1 then it proceeds with the kde1 install, if you are running kde2 with the .kde dir it proceeds with kde2 install and if you are running kde2 with .kde2 dir it also proceeds with kde2 installi also figured out why things weren't being added to the k menu in mandrake...if you use the mandrake-style the k menu (as opposed to the default style) it stores the menu config files in /usr/share/menu instead of ~/.menu so i fixed it so that the menu configs are copied to both locations and everything seems to work well now.  my only concern is if the 1st part of the fix (the one mentioned in the previous paragraph) will work on redhat or not, seeing as i dont know whether the menu configs are stored in ~/.menu or /usr/share/menu.  Anyone that cares to test it out and let me know, feel free..> You should not make that script to cope with every> possible setup. That would > be an overkill.> You should just make it to work with all the major> distros.> Other distros, and individuals with special setup> should change the > wineshelllink before installing or packaging.> see response above> At most you could make tools/wineinstall ask for the> needed info and generate > wineshellink according to it. I like this idea...that may or may not be needed, depending on the outcome of a redhat tester> > Best regards> Zsolt Rizsanyithanks, and you too :)the patch is in the next message


---------------------------------
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-patches/attachments/20020424/1787cc8f/attachment.html