Talk:Installing third party softwares in terminal/Build/KDE4/Windows: Difference between revisions

Page contents not supported in other languages.
From KDE TechBase
No edit summary
Line 10: Line 10:
#*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...)
#*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?
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#USB memory sticks: it would be possible to run kde apps/infrastructure installed on the stick in two ways:
#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 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
##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
#*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???

Revision as of 10:24, 15 September 2007

KDE-Windows Meeting: Notes

Started: jstaniek 11:40, 15 September 2007 (CEST)

Topics:

  1. reducing distribution of the file by keeping a snapshot of files on our server(s)
    • this makes mirroring possible
  2. having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
  3. 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...)
  4. We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
  5. USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
    1. 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
    2. 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???