From kde-usability  Wed Aug 22 21:26:34 2001
From: Ian H <arcaneone () yahoo ! com>
Date: Wed, 22 Aug 2001 21:26:34 +0000
To: kde-usability
Subject: KInstaller revisited
X-MARC-Message: https://marc.info/?l=kde-usability&m=99851526712836

On Monday 20 August 2001 07:56 pm, Aaron J. Seigo wrote:
> 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 su=
ch
> > license.  I remember hearing either earlier this year or late last ye=
ar
> > that InstallShield(main windows installer) was ported to java.
>
> there is also kdeinstaller in kdenonbeta, but kinstaller looks to be mu=
ch
> further along. loki's installer is based on gtk+, and i'd much rather s=
ee
> 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?)
>
> > The problem is that each distro is released with a different set of
> > libraries that the binary needs to be compiled against. =20
> not to mention different paths ...
> > The way other projects have gotten around this is to release a static=
 and=20
dynamic
> > binary of their source. Unfortunately, a static binary of KDE would n=
eed
> > quite a
>
I could be wrong but it seems as though the major distros put out thier o=
wn=20
version of KDE's packages with in a week. This leaves the option of=20
downloading the generic packages (source, binary (static or dynamic)).

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

I think this corrruption proctection should extend from the installation.=
=20
Start by comparing files actually installed to the RPM file lists. Add th=
ese=20
to list of  watched files. When ever RPMs/Apps are installed into KDE ( a=
nd=20
possiably the system at large) the package installer/handler ( or KInstal=
ler=20
) can keep track of dependencies whether the file is in a RPM, tarball, o=
r=20
all by itself. This way there is less of a chance that a dependency file =
will=20
be removed or overwritten if there is still a package that needs it.

For those who like to compile their own packages, they should run=20
CheckInstall ( http://mayams.net/~izto/checkinstall-en.html#checkinstall =
) to=20
generate a RPM or another package of choice so the package handler is awa=
re=20
of the additional files and thier depencies.

Not only would this make the installation and upgrade of KDE easier it wo=
uld=20
go far to prevent problem due to dependencies mix-ups.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

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