Linked by Thom Holwerda on Sun 14th Jan 2007 23:05 UTC, submitted by an Anonymous Reader
This week's KDE Commit Digest tells about an installer for KDE on Windows and the problems the developers encountered setting up a working environment for KDE to run on. Many screenshots included, showing the first applications (such as Konqueror) running natively.
Thread beginning with comment 201871
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: This might actually be a good thing
by boudewijn on Mon 15th Jan 2007 15:18
in reply to "RE[4]: This might actually be a good thing"
Member since:2006-03-05
Autopackage is actually used by the Dutch inland revenue for the linux version their tax return application. You can choose between a tarball or an autopackage. Both work just fine. (It's funny, though, that they choose to go with a motif-based version of wxwidgets for the tax app itself).
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-12-31
@Krok and Melkor:
You can get autopackage for Linux and distributors can provide the .package file on a CD to end users who can just double click it to run.
Many applications such as Crossover office etc come with the Loki installer which is great. I even used to make installers for a Quake 3 mod known as Navy Seals:Covert Ops with Loki's installer.
It even has qt and gtk frontends.
www.autopackage.org
Having said that, most distros provide good package management and dependency resolution capability with yum, apt etc.
Melkor, non geek users are not idiots. They are more than capable of installing packages if they put in some small effort in learning the new OS they switched to. Linux is not windows and expecting Linux to act like Windows is not the smart way to go.