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

List:       kde-core-devel
Subject:    Ksycoca backwards compatibility & freeze
From:       Waldo Bastian <bastian () suse ! de>
Date:       2000-04-03 20:33:04
[Download RAW message or body]

Hiya,

There will be a (small) problem by the time we get to KDE 3.0 (or any other
version which is binary incompatible with 2.0) and before that when people
upgrade KDE versions after 2.0 on a running system.

The problem arises when two different versions of KDE are running which require
different versions of KSycoca. Currently the version of KSycoca on disk must
match exactly in version with the one supported by kdelibs.

I would like to change this so that an older version of kdelibs can use a newer
KSycoca version (on disk). For this to work some (small) changes are needed to 
the way how KSycoca stores some information in the database.

The API will not be changed by this. 

Boring Details:
The function allMimeTypes (and other "all" functions) read mimetypes
sequentially from the database. This will break if newer versions of the
database store more information per mimetype, the old kdelibs will then only
read the old mimetype-info and assume that the extra mimetype info is the start
of the next mimetype. To solve this problem we need to store a list with
the starting position of each mimetype. Then newer version can store more
information per miemtype which will just get ignored by the older version.

Cheers,
Waldo

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