I downloaded the latest installer, went to winkde.org repository, selected latest stable, selected kde sdk/okteta. It installed okteta and runtime (v0.0.2). When it finished I saw it didn't create any "start menu" entries, so I went to the install folder and ran Okteta and I got this error: "The program can't start because kdeui.dll is missing from your computer. Try reinstalling the program to fix this problem." Indeed the dll is mising and from what I see I only have okteta exe file and dll-s and also the msvc dll-s. I also checked the antivirus log file and there was nothing mentioned about kde installer. I tried this on a PC and on a laptop both running windows 7. I was told to try also selecting kde-workspace, but I will not install most of KDE dependecies (akonadi, phonon, kwin, etc.) when I just need a hex editor... Reproducible: Always Steps to Reproduce: 1. Download installer and run it 2. Select latest stable (KDE version), kde sdk, okteta 3. Install 4. Run Okteta Actual Results: Okteta does not start. Error message: "The program can't start because kdeui.dll is missing from your computer. Try reinstalling the program to fix this problem." Expected Results: Okteta starts.
My proposal is to split kde-workspace to a few packages (if kdeui is even there) because it installs to many dependencies that you might not need for the applications you selected.
I was mentioning this bug to someone few days ago on IRC. Was it you? At any rate, okteta should not require any piece of workspace for running fine, so I do not think splittin workspace is a good idea. What needs to be figured in my opinion, why kde-runtime is not enough. It should be for standalone application running.
No it wasn't me :) I discussed this bug here http://saroengels.blogspot.de/2012/08/kde-release-party-osnabruck-and-kde.html ... you can also see where I was told to try kdw-workspace But I agree with you ... either kdeui should go to kde-runtime or it should be in it's own package. And if there are any other dependencies needed they should also be in its own package or added to kde-runtime if it makes sense.
No, kde ui should be inside kde-runtime. Patrick seems to have fixed this bug: https://projects.kde.org/projects/kdesupport/emerge/repository/revisions/c23b38e2434d63d809eb70b4b24353f4b4faa852/diff/portage/kde/kdesdk/kdesdk-package.xml Could you please verify with emerge? I guess, it is going to work in the 4.9 release.
Well if I knew what you are talking about it would be no problem :) At the moment the only procedure I know to install kde on windows is the kde gui installer. Point me to a "tutorial" or a development repository and I will try it.
For okteta you will need a lot of dependencies simply because it is based on KDE (kwin is not actually in kde-workspace, only the oxygen style is, so it is much lighter than on Linux). kdeui is actually part of kdelibs which is dragged in by kde-workspace (thats why I told you to install kde-workspace). I also found the issue yesterday, I will update the installers dependency handling soon, it should work then on the winkde.org server in the coming days (I will announce that here).
I can confirm that I had installed KGet and received an error saying that kdeworkspace.dll could not be found. The package kde-workspace-cv100 had not been installed. KGet worked fine once this package was manually installed.
http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=markup Seems KGet has an optional kde-workspace dependency so we could either add that to the python package file or we could avoid having kde-workspace installed when building KGet. Perhaps, there are other approaches. What do others think?
We could also perhaps add an xml file and define this dependency only for KGet for fine tuning if other kdenetwork packages (like kppp) do not depend on kde-workspace.
This is not an installer problem - moved to buildsystem category
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.