| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
klik://wesnoth-latest
klik://wesnoth-latest
Posted Oct 7, 2005 15:58 UTC (Fri) by erich (subscriber, #7127)In reply to: klik://wesnoth-latest by lovelace
Parent article: The Battle for Wesnoth hits 1.0
I don't see a point in using klik, except to make my system behave less predictable (and thus less stable).
klik reminds me a lot of autopackage, which I think is a very bad concept.
Also how is klik supposed to e.g. prevent things like the C++ API differences?
No, I'm really happy with my distributions dependency management, so I do not intend to install anything else.
(Log in to post comments)
klik://wesnoth-latest
Posted Oct 9, 2005 13:12 UTC (Sun) by farnz (subscriber, #17727) [Link]
Klik differs from autopackage in that klik does not expect to install stuff onto your machine. It just downloads the files needed to run the application into an "AppDir", and runs it from there. See the architecture documentation for full details. It therefore cannot conflict with your distribution package management (unlike autopackage), and uninstalling your klik packages (restoring the system to its lack-of-klik state) is a simple case of deleting the downloaded AppDirs (which won't conflict with anything from the distro).
klik://wesnoth-latest
Posted Oct 14, 2005 14:57 UTC (Fri) by quintesse (subscriber, #14569) [Link]
Which is not entirely true of course if the package makes system-global changes like file associations, menu items, icons, etc. Especially if those were taken by an existing program already.
But at the same time I'm sure that in the end those problems can be fixed or worked around.