Yes, it does need to be updated - for sure.  Sorry.  We have not
looked at those pages in a while.  I will dig into it.  In the mean
time if you have any questions about the directory structure or
workings of the tools just ask.  Basically the directory structure now
looks just like that of OTP.  Basically we have

erlware
  * bin - for executable start scripts
  * lib - underneith lie the application directoies in the form
<appname>-<appversion>
  * releases - underneath lie release directories which are of the
form <relname>-<relvsn>. These release dirs contain the .boot files
and any .config files as well.
  * erts-<vsn> - these are the actual erts packages


Cheers,
Martin

On Sat, Sep 26, 2009 at 12:41 PM, hqmq <[email protected]> wrote:
>
> Hey All -
> If I missed something obvious in the tutorials I apologize, but I
> tried to walk through the tutorial here: 
> http://www.erlware.org/erlware/tutorial.html
> and failed multiple times.
>
> Most of my confusion comes with the directory structure. I think it
> might just be out of date, but some of the directory listings and
> structure descriptions in the tutorial don't match what sinan actually
> generates.  Also the bin script that it suggests assumes an erlware
> structure that doesn't match what faxien set up on my machine( ie. a
> directory called release-packages under /usr/local/erlware).
>
> The reference manual for Sinan (http://www.erlware.org/tools/sinan/
> reference.html) looks more accurate to what I see on my machine.  Is
> anyone else seeing the same thing?  Does the page just need to be
> updated?
>
> Thanks,
> ~Michael
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"erlware-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/erlware-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to