[e-lang] a few notes about E install/basic usage

[Zooko O'Whielacronx]

>> I just tried to install E again.  First I tried compiling from
>> source, which failed, and I didn't diagnose why (yet) but instead
>> downloaded the "pure j" tarball.  I executed my old inst-e.bash
>> script, and it complained that it couldn't find a "dist" directory,
>> so I mkdir'ed a dist directory and moved everything except for inst-
>> e.bash into it and then, I was glad to see, inst-e.bash just worked.
>
> inst-e.bash was apparently written to work on a source distribution
> root. dist/ is the directory from which compiled distributions are  
> made.
>
> Please rewrite inst-e.bash to work with the purej distribution --
> right now, there's a nonworking copy of it included, and that's bad.
> If you supply a fix I'll commit it.

It currently works, if you do:

mkdir dist
mv * dist
mv dist/inst-e.bash .
./inst-e.bash

Therefore, we could change inst-e.bash to "cp -a ." instead of "cp -a  
dist".  Would that satisfy?

>> I finally hit an irritating snag and stopped for now.  This was when
>> I wanted to import some E code from a file into the interpreter.  To
>> do so, according to Walnut [1], I need to import my module as
>> something like <import:com.yourdomain.e.makeQueue>.
>
> You can do this:
>
> <elang:syntax.EParser>(<file:makeQueue>.getTwine()).eval(safeScope)

Thanks for the tip!  Should this live in the Wiki Walnut so that  
other folks like me don't get snagged by the Java namespace issue?

>> 4.  After I held my nose and went through the hassle of mkdir "/
>> System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/
>> ext/emakers" and symlink my file so that it is reachable from that
>> directory, then it still didn't work.
>
> Ack, don't do this. Use the -cpa option to rune instead.

Thanks for the other tip!  I read the output from "rune --help"  
several times and didn't see this option...  Next time I play with E  
I'll check if that can be improve somehow.

Regards,

Zooko