+1 I'd like to take that further.
How about having a .sinan-rc file in which we can place arbitrary Erlang "pre" shell (and maybe even pre-build) code as well as additional (or modified) erlexec command-line parameters? I am running into issues now where, if things don't fit the Sinan model (and many things out of my control don't), I am either forced to hack or give up. What is needed is some extension mechanism that allows the developer, at his or her own risk, to set up the environment for the build (and for the shell). In addition to that: - I'd like the ability to add my own custom tasks, just like you can in Ant, without hacking the base code - I'd like a standard "execute this operating system command" task. This could be used to invoke, say, a make from within Sinan. Why? Because with things like Yaws, configure is used, and source code is generated using their Makefiles. I don't want to hack on 3rd party makefiles and the .app files, let alone their source code. What I am currently doing now is using a Makefile that first calls the Yaws configure script, then its make, and then Sinan (which goes and rebuilds what the make already made, but what the heck). - I'd like faxien to be able to put a standard tar into the repository as built by the Erlang release system. Maybe it can, but when I tried using Yaws (which can generate a release tar file), I had problems. Generally speaking, I think ideas should be taken from Ant to provide a more extensible and customizable situation. I am all for convention over configuration, but only when everyone agrees to stick by the convention. Even Rails has mechanisms to override the conventions because there are so many situations where they are not stuck to. Now this is not a rant, only some feedback from a person that has two fairly complex Erlang-based production applications that use multiple external packages, including RabbitMQ, OSERL, ibrowse and Yaws. You have to understand that I wanted to do a flash-cut conversion to Faxien/Sinan over a 3-4 day period, and it's day 3 :). If I fail, then it's back to make/tar/ftp/untar + hours to get everything working right for each update. I really don't want to fail :D Regards, Edwin On Sep 5, 6:27 pm, "Matt Williamson" <[EMAIL PROTECTED]> wrote: > Hey Guys, I'd like to specify -boot <release> for sinan shell. Can I do that > somehow? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
