But can you use klik to build a local databse of the repository that include package headers, dependency information and such? dpkg's and rpm's create a local database with all that info. So far, klik installs the software in a directory and creates a "wrapper" file to run the application with the relevant paths set to directories inside the installaition tree (from what I saw). I can't seem to do that with more sophisticated packages like Tex/LaTex which require lots of shared libraries as deps. (WHY DID THEY REMOVE IT FROM THE KNOPPIX CD????? WAAAH!). Are you currently working on resolving all of these issues?