First off: Though Arch is not an "officially" supported distribution, I know that ArchLinux users in fact have reported that they made klik work for them by only a few minor tweaks.

I'll list a few of the "base" requirements for the klik client to work in the "User's FAQ" (http://klik.atekon.de/wiki/index.php/User's_FAQ).

The fact that your system is ArchLinux doesnt mean that klik will install an RPM to your system. It will do this:

--> *download* an RPMs, .debs or .tar.gzs into your /tmp directory (if these file formats are used to produce a klik .cmg);
--> use rpm2cpio to extract any .rpm that is amongst the downloaded ingredient files;
--> convert the ingredients into a single .cmg file (the klik native file format);
--> delete the ingredient RPMs, .debs or whatever from your /tmp again.

You only really *need* to have the rpm2cpio utility on your system for those few klik recipes that use RPM ingredients with their recipe. Arch doesnt install rpm2cpio by default, because Arch's package format doesnt use RPMs.

Most of klik's recipe's however do use .debs as input ingredient files exclusively. Very few have RPMs (mostly because there are now .debs available which provide an equivalent version).

I hope this makes the process more clear to you .