Version:           1.2 (using KDE 3.4.2 Level "b" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-20a-default

Carsten,

I saw your "complaint" in #scribus that the klik://kalzium link didnt bring you a single additional bug report. Well, now wonder: 

 a) you didnt promote the possility yet, did you?

 b) what <a href="klik://kalzium">klik://kalzium</a> currently delivers is version 1.2

Here is how you can fix that:

* provide a stable link (I suggest to name it "kalzium-latest")
  that has always the compiled version you want to be tested.

* compile this binary preferrably in a Debian Sarge environment
  (this way it is more portable to other distros)

* build against kdelibs 3.3 (if this doesnt hurt your app's
  functions too much)

* preferably, build .debs (or find someone who does)

* otherwise, provide just a *.tar.gz with all the binaries, libs,
  .desktop and asssorted files

This way, we can set up a <href="klik://kalzium-latest">klik://kalzium-latest</a> link, which will deliver a "recipe" to the klik client that will download your .tar.gz (from whereever you can host it) and let the client transform it into a klik-ified .cmg file. Then blog about it (or do some other ringing, whisling, shouting, belling) whenever you want people to testdrive a new binary development release. (Ok, we may need to have 2-3 iterations of the recipe before it works fully and for most people).

Just try <a href="klik://scribus-latest">klik://scribus-latest</a> to see how well this works. If you watch closely, you'll see which binaries the klik-client downloads (.debs from debian.scribus.net), because klik informs you with a kdialog popup before it proceeds.

It is up to you to utilize this service for your development effort.


Cheers,
Kurt