Following up on the issue we were discussing this morning. Here is how the problem is solved in dev in a pretty non-erlware way. Each project is either an app or a release right. If an app then just build it. If a release, then it specifies certain applications at a specific erts version.
We use our package manager against a release file within a project. The package manager brings down the appropriate package versions and places them in _build/lib or .lib or somesuch within the project space. sinan has that location on it's path. sinan also accepts a beam_path config or env var which indicates where any other local apps reside so that if you want to have central system you can. Thoughts? -- Martin Logan Erlang & OTP in Action (Manning) http://manning.com/logan http://twitter.com/martinjlogan http://erlware.org -- 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.
