Linked by Thom Holwerda on Fri 16th Sep 2005 21:02 UTC, submitted by Josh
Linux Klik is a system which creates self-contained packages of programmes installable over the web with a single click. In this article Kurt Pfeifle discusses the potential uses of this technology for helping the non-coding contributors to KDE. He also looks at how the system works and the obvious security issues involved.
Thread beginning with comment 32572
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: well..
by on Sat 17th Sep 2005 11:38 UTC in reply to "well.."

Member since:

I don't see how is it in the style of OSX though.

As in drag & drop style installing. The application is statically linked, all the libraries it depends on are compiled within the application, it doesn't depend on system installed libraries. This is to cure the so called 'dependancy hell'.

The downside is statically compiled applications are much bigger in file size, but nowadays this shouldn't be a problem but it also makes updating more cumbersome. Instead of updating a dynamic library, zlib for for example used in all c apps, you have to download updates for every application. If you want to keep up with security updates that is.

I use OSX and really like the drag & drop but i still prefer the debian way.

Reply Parent Bookmark Score: 0

RE[2]: well..
by jziegler on Sat 17th Sep 2005 21:10 in reply to "RE: well.."
jziegler Member since:
2005-07-14

Not only are their bigger on disk (no-one cares), on the network (some might care + compression helps), statically linked apps are bigger in RAM as well and that still hurts.

I too prefer using a system, which know which files to download, to searching and downloading the files one-by-one.

On the other hand, some of the proposed uses are good - install without having root, easy to install for non-technical types (translators, UI designers). For these reasons, I wish the luck and success with this project, though I probably won't use it.

Reply Parent Bookmark Score: 2

RE[3]: well..
by on Sat 17th Sep 2005 21:50 in reply to "RE[2]: well.."
Member since:


Not only are their bigger on disk (no-one cares), on the network (some might care + compression helps), statically linked apps are bigger in RAM as well and that still hurts.

This isn't very relevant if you include commonly used libraries in the base system. Non-commonly used libraries would be rarely needed, and thus wouldn't be much of a disk-space waster.

-bytecoder

Reply Parent Bookmark Score: 0