Figure out bootstrapping

[oubiwann]

Bootstrapping lfetool

LFE projects are created with the understanding that lfetool is installed and available. If, however, we were to make lfetool a project that had dependencies such as erl and LFE (and other deps in a rebar.config), we have to consider things more carefully.

Here is a list of lfetool commands that can be executed without Erlang installed:

• lfetool install lfetool
• lfetool install expm
• lfetool install kerl
• lfetool install erlang
• lfetool install erjang

The following need at least Erlang (since they install into a directory obtained by making erl calls):

• lfetool install rebar
• lfetool install relx
• lfetool info *

The following require lfetool to be installed:

• lfetool update *
• lfetool repl *

The following require LFE:

• lfetool new *
• lfetool tests *

  Bootstrapping Other Projects

• What about installing Erlang itself (via kerl)?
• What about rebar?

[oubiwann]

So, my first thought is to handle that first batch of install commands in the shell script, and everything else as options in an LFE command parser module.

[oubiwann]

Bootstrapping for lfetool version 2 might look like this:

• download lfetool shell script (e.g., from github)
• execute lfetool bootstrap; this would do the following
  1. run lfetool install lfetool (optionally provide install path to bootstrap command)
  2. create the ~/.lfetool/ directory, if it doesn't exist
  3. download github.com/lfe/lfetool repo to ~/.lfetool/lib
  4. compile lfetool code in ~/.lfetool/lib/src to ~/.lfetool/ebin
  5. compile lfetool plugins in ~/.lfetool/lib/pluginsto ~/.lfetool/ebin
  6. compile user plugins in ~/.lfetool/plugins/ to ~/.lfetool/ebin

At this point, everything will be availale for use.

[oubiwann]

Added code that can be used to bootstrap plugins in d803117. This is a function that will compile all plugins, official as well as user-created.

[oubiwann]

See related: issue #81.