
For developers (as of 20 Jan 2006)
----------------------------------


Information about installing erlmerge somewhere else than
$(ERLANG)/lib.
If you are want the default install directory skip to ''Install it as:''

Otherwise, before running make, change directory to config and do:

./configure erlmerge_install_top=</where/you/want/it>
This will install the erlmerge script as
</where/you/want/it>/bin/erlmerge
and the erlmerge application as
</where/you/want/it>/lib/erlmerge-<vsn>

Then back up to this directory and follow the description below.


Install it as:

make
make install  (as root if 'erl' is installed as root) 

This will create a directory and a DB:

 ..../erlmerge_DB/erlmerge.dets

The DB will be filled with info about the existing apps.
List them with the command:

 erlmerge search
 erlmerge search mnesia

Check the 'Installed' info, it should be 'true'

Now sync the DB with the latest stuff from trapexit.org:

erlmerge sync   (again as root if necessary)

This will store the sync info in:

 ..../erlmerge_DB/sync.erlmerge

Those that are located behind a firewall/proxy should do:
erlmerge -z <proxy>:<port> sync

If the connection times out before the information has been transfered,
try to increase the timeout by doing:
erlmerge -t 30 sync


Search the DB again and look for 'eldap' and 'eradius'
They should not be installed.

Now, to install an application do as in this example:

 erlmerge -i esmb

or for a dryrun:

 erlmerge -p -i esmb

The '-i' (or 'install') switch will retrieve the application
and all its dependencies, unpack them and compile them
under your $(ERLANG)/lib directory. So, for example, the
application esmb may end up as a directory:

 /usr/local/lib/erlang/lib/esmb-1.0/

Which will make it available when you start your
Erlang node/shell.

If you installed erlmerge somewhere else (see ''erlmerge_install_top'')
you might have to add this lib directory to the erlang search path upon
startup. See ''-pa <Directory>'' in the man page for erl.


Note for developers: erlmerge will use an ''Emakefile'' if present in
the top level directory of an application. If the application is
written in erlang only, an ''Emakefile'' with the following contents
would compile and install all modules:

{'src/*', [{outdir, ebin}]}.

It is assumed that the application has the same Basic File Structure as
''base-1.0'' shown in:
http://www.trapexit.org/docs/howto/release_handling_tutorial.html.

