Quote Originally Posted by probono
Hi Samuel,

why don't you join the klik project instead of making your own implementation? (There is always a bunch of klik developers on #klik on irc.freenode.net that would like to work with you...)

As for compiling, I can't help you since I never compile anything. klik always uses binaries that are already on the web.

Greetings,
probono
Thanks anyway probono, I would like to join to the klik project but I want to be sure to be useful so I want to finish some testings before reporting some results. By the way, there is one thing that I don't like from the klik project. Although I don't know more than the docs in the website, I think there is a great dependency on Debian GNU/Linux, APT and .deb packages (as fas as I know the klik cmg are created at server side with deb files, or isn't?).

My project is based on LinuxFromScratch, I'm creating XML profiles (www.linuxfromscratch.org/nALFS) to automatize the package compilation. At the XML you can choose three kind of installation. 1. Install normally (make install) 2. Create a cmg package (now KDE packages only are the target) or 3. Create a binary tarball (this is because I have in mind to create or use some installer for the base packages, and the cmg for the rest of apps).

What I've made is a simpler zAppRun and a Wrapper, just thinking on my own desires

Basically that's my idea. All the cmg stuff is credited to the Klik people (you and others ), FUSE people (i'm using fuse), and FUSEISO author. Ouch! The Linux From Scratch people does most of the job in my project! Thanks to everybody!

Probono, maybe this could be the beginning of a Klik based "distribution"?? (I prefer to call it OS because I'm breaking many LSB standards for the sake of enduser commodity).

Samuel.

PD: Excuse my english if there are some mistakes.