OK... let me try to clear up some of the confusion here...

First off, the "Incompatible application package" usually stems from one problem: the section field of the package. Packages that the user normally wants to install, and packages that the application manager shows you are in some user/* section. Libraries, and packages that you really don't need to install by themselves, things just depend on them, are not in a user/* section, so the application manager throws the very uninformative "Incompatible applicaiton package" error. [edit]Looks like Bundyo also explained this in the post above... I just took too long to type this

Second, installing applications on the tablets IS a "one-click process" if that application is in a repository. You've probably noticed this when installing other application: just click, wait, and you've got an application. That's more than I can say for ANY windows program. (Usually, run the installer, click Next, check that you agree, click next, verify install location, click next, choose where you want shortcuts, click next, wait for install, click next, choose to see readme or run the application, and click finish.) I would hardly call this "one-click". The problem on debian arises when you try to install a package you downloaded as a deb. In this case, the dependencies will NOT automatically be filled (for package safety reasons, I believe... not sure if this is configurable anywhere...) Generally, though, applications are in repositories, and dpkg will throw an error if there are missing dependencies that you just need to apt-get install.

Finally, all these problems can be avoided with the tearbookmarks package with the help of some advice I've been trying to avoid giving: enable extras-devel. If you do this, the package will show up in your applications list. However, beware! Do NOT upgrade anything it says is upgradeable, or install anything else. After you install the bookmark plugin, DELETE extras-devel. It's really only meant for developers, and unstable/not-ready-to-be-released packages, and some crazy stuff can happen if you keep it enabled.

Having said all this, I'm only holding off putting the bookmark plugin in extras for two reasons: one, it's incomplete; two, I'd like to merge it with the bookmark manager; three, I'm waiting for tear to be in extras. In order to be complete, the bookmark manager has to support folders. I'm working on this code, but having a bit of trouble with it... stay tuned! I still need to work with Bongo a bit on implementing some of his code, and getting a package with his bookmark manager and my plugin together. And, of course, this package is useless without tear, so there's no point in having it in extras if tear isn't there. It would only confuse people.

Qole: Could you maybe stick the tasknav plugin in your repository? That should clear up some of these issues, without having to put it in extras.

If I'm wrong or oversimplifying anything here, please feel free to correct me! Learning is an ongoing process