[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Redhat 7.1 and KDE2.2 are go! - But not for everyone
From:       "Aaron J. Seigo" <aseigo () mountlinux ! com>
Date:       2001-08-20 23:56:44
[Download RAW message or body]

On Monday 20 August 2001 17:28, Jim Conner wrote:
> Well, the KInstaller project has been mentioned.  Also, Loki has an
> Installer that they use for their games.  I think it's GPL or some such
> license.  I remember hearing either earlier this year or late last year
> that InstallShield(main windows installer) was ported to java.  

there is also kdeinstaller in kdenonbeta, but kinstaller looks to be much 
further along. loki's installer is based on gtk+, and i'd much rather see an 
installer that looks at home on kde. i don't think java is a good solution 
either (if InstallShield would even work very well on linux. anybody tried?)

> Unix. The problem is that each distro is released with a different set of
> libraries that the binary needs to be compiled against.  The way other

not to mention different paths ...

> projects have gotten around this is to release a static and dynamic binary
> of their source. Unfortunately, a static binary of KDE would need quite a

a static build still wouldn't work since the C++ ABI varies from distro to 
distro depending on the version gcc installed. within the next 2-5 years the 
C++ ABI on all gcc platforms in use will probably be uniform (due to gcc3).

> use a similar format. Just had a thought.  User X upgrades KDE2.x to
> KDE2.2.  For example, KMail has changed format of it's config files and
> breaks when loaded because user hasn't removed /$HOME/.kde(2)/.  Wouldn't
> it be easier if when KMail loaded, it recognized the older config file
> format and converted it to the new format?  There can even be a simple

this is a very good idea, so good in fact that there is already such a 
facility available (since 2.1) that allows upgrading config files ... as a 
bonus it doesn't require adding useless cruft directly into the application 
in question to check for older config files every single time it is run.

one of the common problems w/config files in total corruption. this will 
hopefully be largely fixed when KConfig gets some checksumming capabilities 
(which it apparently is according to some devel discussion last month). 
KConfig will be getting some large-ish overhauls for kde3.

-- 
Aaron Seigo
-- 
Aaron Seigo
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]