We are thinking about making a significant addition to sinan that has the potential to affect the users in a significant way. This change revolves around giving the user the ability to override Sinan's default dependency and release handling capability via providing a custom *.rel file.
Sinan would pull the dependencies from the *.rel file if it exists and ignore it otherwise. The rel file would be in the normal *.rel format. There would have to be a few variations to support things like build flavers. Here is what I propose for that. Search path in order of precidence <root>/releases/<flavor>/<name>-<version>.rel <root>/releases/<flavor>/<name>.rel <root>/releases/<name>-<version>.rel <root>/releases/<name>.rel of no release file existed at any of these locations it would ignore it generate a rel file as it usually does. Of course, the apps and versions supplied in the custom *.rel would be the dependencies that the system relies on. I think there are probably a bunch of other use cases people could thing of, so I am throwing this out as an RFC. -- 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.
