Translations talk:Installing third party softwares in terminal/Build/KDE4/Windows
Revision as of 19:52, 16 September 2007 by 220.127.116.11 (added msi evaluation, added debus merge problems)
This section needs improvements: Please help us to
cleanup confusing sections and fix sections which contain a todo
KDE-Windows Meeting: Notes
Started: jstaniek 11:40, 15 September 2007 (CEST)
- reducing distribution of the file by keeping a snapshot of files on our server(s)
- this makes mirroring possible
- having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
- we need unstable releases to get people test software early and often and on Windows
- 'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
- development installation requires tools having own installers
- ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
- We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
- USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
- If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host conuter could be reused
- If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
- In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
- format of the kde mirrors:
- Insert compiler name into package and manifest file name (msvc, gcc)
- snapshot releases with debugging information
- New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
- Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
- dbus for win32 is working mostly for recent kde applications, although there are some issues:
- A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
- if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
- Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
- There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
- There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
- win32 issues with the cmake build system (TODO: list the issues)
- install system topics:
- it is planned to evaluate the microsoft windows installer for releasing kde windows application.
- if msi is not usable the kdewin-installer should be extended with the following features:
- update function
- simplified end user interface
- integrity checks (md5 package and file checks)
- cd/dvd/usb stick installation
KDE on Windows can be called the first official KDE-own distribution
Content is available under Creative Commons License SA 4.0 unless otherwise noted.