Linked by Mike Hearn on Fri 6th Dec 2002 08:37 UTC
Linux If you've used Linux for more than ten minutes, you've almost certainly come across the nightmare that is package management. You know what I mean - dependancy hell has become legendary and it's no exagguration to say that one of the most offputting aspects of Linux for a new user is the lack of InstallShield type 3 click installs. This article looks at how we ended up in the quagmire of RPM and dependancy hell, and then moves on to talk about a possible solution in the form of autopackage. It takes a high level overview of how autopackage works and what it's capable of. If you want more technical details, check out the website. Finally, this article assumes only that you're interested, not that you have any Linux experience.
Permalink for comment
To read all comments associated with this story, please click here.
Er... Java and clear installation...
by Xavier on Fri 6th Dec 2002 23:36 UTC

When you have finish with the sdk, the ee engine, a little jre to test client, put jdbc jar files to the right directory, try to find a intelligent classpath file ( approx 2 hundred lines... ), you are ready to install jakarta aka tomcat / ant, don't make any error on classpath..., well and now ready for some jswat, be carefull with the classpath..., some junit, back to jakarta / regexp to also test swing, don't forget the classpath, and, phew, ready for some xml, xerces, xalan, a little xindice, back to jdbc jar file..., cocoon to link them, phew, be carefull with the classpath ( now 4 hundred lines, and, obviously, no error... ), maybe are you ready now for some corba orb ? Not to bore you too much, i avoid versioning problems... But maybe a little word about chmod and chown to secure all this, just before looking at the proxy and firewall, of course if you're a fan of corba, do not hesitate to link all this to orbit and xinetd.

But that's apart, installing Java in child simplicity : it's rock ;-)))