hmm, why abstract away the control over the release file? Would it be hard to add the actual release syntax into the config file - oh, and remove that json and turn it into erlang terms while you are at it :)
On Fri, Jun 11, 2010 at 4:56 PM, Tristan Sloughter <[email protected]> wrote: > An included application is specified in the application that includes it > .app file. The .app file has the property applications and > included_applications, both of which are lists of apps that are dependencies > of that application. If the app is in the included_applications list when > the release file is generated it will be marked as 'load'. > All versions are dependent on what you put in each applications .app file. > Only the version for the release itself can be specified in the .cfg file. > > On Fri, Jun 11, 2010 at 4:39 PM, Martin Logan <[email protected]> > wrote: >> >> This is great. I want more info on releases. If I want to nail down a >> release and all its internal versions where do I put that information? >> Where do I indicate an app is only included. I usually do that in the >> release file with the 'none' atom. >> >> Nice work, this sounds like good step in the right direction. Now we >> just need to kill the long running server thing :) >> >> On Fri, Jun 11, 2010 at 4:17 PM, Tristan Sloughter >> <[email protected]> wrote: >> > Sinan 0.17.0.0 released >> > Changes: >> > >> > * On exit Sinan now returns a proper status code. Codes: >> > 1 general error >> > 2 (reserved for bash misuse of builtins) >> > 3 cant connect >> > 4 build error >> > 5 cant start server >> > 130 terminated by ctrl-c(bash standard) >> > * Sinan now properly handles included applications and their >> > dependencies, >> > meaning none are started buy only loaded on starting a release. >> > * Added ability to define multiple releases to be built and a option for >> > sinan dist to specify which release to be built. >> > Multi-release example using sinan as the project: >> > In your _build.cfg append: >> > releases : { >> > sinan_no_web : { >> > vsn : "0" >> > apps : ["sinan"] >> > } >> > sinan_with_web : { >> > vsn : "0" >> > apps : ["sinan", "sinan_web_api"] >> > } >> > } >> > In this example I give the option to build an executable that does not >> > include sinan's web api and one that does. Notice I do not have to >> > specify >> > the dependency of 'etask' which IS included in the release since >> > sinan >> > depends on it. >> > You could then use 'sinan dist -r sinan_no_web' to build the release for >> > sinan_no_web. >> > Sinan dist also works just as it did before if you do not specify a >> > release >> > and build a release containing ALL project apps. >> > Tristan >> > >> > -- >> > 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-questions" 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-questions?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.
