|(14 intermediate revisions not shown)|
Latest revision as of 23:21, 20 April 2011
E-on-Java Download Page - licensed under Mozilla or Mozilla compatible open source license.
Zero Install feed
On a clean install of a modern Linux distribution, you should now also be able to get and run E like this:
$ 0alias rune http://repo.roscidus.com/e/e-core $ rune ? println("Hello from E!") Hello from E!
You will be prompted to accept Thomas Leonard's GPG key (DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA). If you don't have the 0alias command you will probably be prompted to get it from your distribution. If not, you can use one of these commands:
$ sudo apt-get install zeroinstall-injector # Debian or Ubuntu # yum install zeroinstall-injector # Fedora
It should automatically pull in the OpenJDK 6 JRE if you don't have it already. Binaries for x86 and x86_64 are currently available, but we can add more easily if needed. On Fedora, an SELinux box may pop up if your policy prevents you from running Java; either edit the policy or disable SELinux. It hasn't been tested on other distributions, but it should work. If your distribution is too old to have 0alias, you can get it directly from the http://0install.net/ site.
The "e-core" package only contains the E runtime ("e.jar" and "rune", basically). It does not contain the example scripts, CapDesk, etc, and it does not depend on SWT, as people might not want all of that just to be able to run E programs. It is currently based on svn trunk, plus a minor patch for a race condition and changes to the build to exclude unnecessary bits and to provide a working "rune" out of the box (no "rune-template"). The changes can be seen here: http://gitorious.org/repo-roscidus/e-core/commits/master
There is a separate e-swt package that depends on e-core and on SWT, which you can use like this:
$ 0alias rune-swt http://repo.roscidus.com/e/e-swt $ rune-swt someprog.e-swt
The packages do not register file associations (Zero Install installation is side-effect free), but this shouldn't be a problem. Developers will probably want to run their programs using their rune or rune-swt aliases, and users will normally get a package with a dependency on the right "rune", resolved automatically through the package metadata, rather than double-clicking on a raw .e file.