Well I think the argument is that it really is an Erlang problem, not really in the scope of sinan, but if maybe we could have it work around the problem.
Right? Thanks! Jordan Wilberding On Sat, Feb 5, 2011 at 1:38 PM, Tristan Sloughter < [email protected]> wrote: > Ah, so now I understand the problem you and Eric were talking about. For > some reason the fact that apps are installed to lib/, a single dir, and > can't be separated out by Erts version was not on my radar when you guys > were talking. > > Really, I think its sad it can't be done that there is a lib dir per erts. > But maybe that would cause other problems? Isn't that what Java does? And > linux with lib64/ and lib/? > > Obviously if that were possible its not in the scope of sinan. > > Tristan > > > On Sat, Feb 5, 2011 at 12:22 PM, Martin Logan <[email protected]>wrote: > >> 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]<erlware-dev%[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]<erlware-dev%[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.
