Thursday, March 02, 2006

Klik - Installing Softwares from Browser

Till now I have been using urpmi (software manager for Mandriva),
Until I found klik a browser based installation which works with kde.

Klik focuses on application bundles that contains all the basic libraries
needed to execute the program.

Installation of softwares can be done by way of typing

klik://packagename in the browser

You can check the list of packages available here

Now Installing klik:

Please note I am using Mandriva 2006

1) Login to your KDE Desktop as Normal User(sriram).

2) GNU C++ library is needed on Mandriva 2006

#urpmi libstdc++5

This will install all the needed dependency.

3) Install the klik client:

press [Alt]+[F2] and paste:
wget -O - sh

In Console it will show up like this :

=> `-'
Connecting to klik.atekon.de134.169.172.48:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14,890 (15K) [text/plain]

100%[====================================>] 14,890 12.19K/s

17:56:24 (12.18 KB/s) - `-' saved [14890/14890]

8514 ? 00:00:00 mozilla-firefox
8527 ? 00:00:00
8532 ? 00:04:26 mozilla-firefox

Follow the instructions that pop up on your screen.

4) Now in the console login as root and run the below command:


This is bcoz your /etc/fstab need to be setup to use cmg files.

Sometimes you wont find this file - No worries, you can carry ahead.

5) If you have mozilla browser opened pls close it and reopen it once.

Now type the below in your Mozilla-firefox browser.


xvier - is a game of 600kb.

If you are bit security concerned, you may want to know what klik does to your system. Here's the pitch:

  • Its .cmg files are self-contained AppDirs (applications directories), compressed into a cramfs or zisofs file system.
  • To run the contained app, klik mounts the bundle file underneath /tmp/app/1/ and runs it from there; if mounted, the bundle looks like it is a subdirectory expanded into the real directory structure of the host.

If you are even more cautious, or paranoid, you surely want to investigate more closely and see how klik operates on your system. Follow these steps to find out more details:


(this downloads the install file without executing it).

less install

(this lets you look at the installer code: fear not -- it's pure shell).

less $HOME/.klik

(this lets you look at the "commandline client+klik protocol handler" code, of course only after running the klik client install).

less $HOME/.zAppRun

(this lets you look at the commandline starter for klik-ified AppDir bundles, also executed if you just click on one of the .cmg files).

less {$KDEHOME,$HOME/.kde}/share/services/klik.protocol (the secret behind the klik://my_cool_app links, part 1).

less {$KDEHOME,$HOME/.kde}/share/applnk/klik/klik.desktop (the secret behind the klik://my_cool_app links, part 2).

less {$KDEHOME,$HOME/.kde}/share/applnk/klik/.directory (why there is now a klik icon and a klik entry in the K Menu).

less {$KDEHOME,$HOME/.kde}/share/mimelnk/all/cmg.desktop (why klik is now responsible for handling clicks on files that happen to have a .cmg suffix, part 1).

less {$KDEHOME,$HOME/.kde}/share/applnk/.hidden/AppRun.desktop (why klik is now responsible for handling clicks on files that happen to have a .cmg suffix, part 1).

less /etc/fstab (why klik can now find mountpoints in the file system to mount the .cmg AppDirs on execution).

ls -lR /tmp/app/{7,6,5,4,3,2,1} (list the directories underneath the mountpoints while one of the .cmg AppDirs is executed).


A few applications don’t open or crash. Some place the .cmg file in your home directory instead of your desktop, and some never move the .cmg file from the /tmp/klik directory, so you’ll have to move them yourself. Others necessitate that you run the klik package via the command-line, using ~/.zAppRun /path/to/package.cmg

You can find the logs for klik in /tmp/klik/klik.log