It's a good idea obviously. I actually miss that a lot using our old pal sinan, when it just slaps you saying "I'm not going to compile this until you place its name in the stupid app file" :D (I'm joking, of course. I was up to propose the idea, but I'm now expectant for the new tools).
Aside, it seems we are in another turn of the wheel. Many different people trying to make something sensible around release generation and OTP rules. Apart from erlware, I'm seeing rebar (http://dizzyd.com/blog/post/194) more and more, I got pointers to a maven plugin (http://sourceforge.net/projects/erlang-plugin/), OTP team may be taking seriously their rel_tool, etc. It's a pity that no project builds enough mass to get mainstream (of course, I'd like that project to be erlware). On 20 October 2010 20:00, Eric Merritt <[email protected]> wrote: > I am not actually sure. I haven't looked into rel tool since its initial > release when when it was pretty easy to dismiss. After taking a quick look > its probably worth looking at again. > > > El oct 20, 2010, a las 12:51 p.m., Anders Nygren escribió: > >> Hi >> Doesn't rel_tool do most of that? And its part of OTP. >> >> /Anders >> >> On Wed, Oct 20, 2010 at 12:35 PM, Eric Merritt <[email protected]> >> wrote: >>> It's open under a permissive license no problem reusing >>> >>> Enviado desde mi iPhone >>> El Oct 20, 2010, a las 12:34 PM, Martin Logan <[email protected]> >>> escribió: >>> >>> Very cool - you should get in touch with him and see about reusing there >>> code. >>> >>> On Wed, Oct 20, 2010 at 10:45 AM, Eric Merritt <[email protected]> >>> wrote: >>>> >>>> Guys, >>>> >>>> Sinan could do this trivially. I am thinking about it in line with the >>>> new release stuff. >>>> >>>> >>>> http://dukesoferl.blogspot.com/2009/05/automatic-app-file-generation.html >>>> >>>> Eric >>>> >>>> -- >>>> 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. >>>> >>> >>> -- >>> 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. >>> >>> -- >>> 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. >>> >> >> -- >> 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. >> > > -- > 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. > > -- Samuel -- 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.
