Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bear is not listed in .app.src dependencies #82

Closed
arjan opened this issue Jul 17, 2014 · 5 comments
Closed

bear is not listed in .app.src dependencies #82

arjan opened this issue Jul 17, 2014 · 5 comments

Comments

@arjan
Copy link

@arjan arjan commented Jul 17, 2014

Therefore, running folsom from an Erlang release results in an error because bear is not packaged.

@linearregression
Copy link

@linearregression linearregression commented Jul 30, 2014

I did not run into this issue when I recently did an Erlang Release on folsom_webmachine (not folsom itself) successfully. Just to clairfy, are you making an OTP release for folsom? If you are below is what I did.

Since folsom_webamchine includes folsom and all its deps, I bet it is similar
For my case, I need to add bear (any other libraries crypto?)
{app, bear, [{incl_cond, include}]},
to reltool.config in the rel directory <------
before rebar generate

rebar supposed to figure this all out, but it has not been extremely consistent for me.

Hope this helps.

@arjan
Copy link
Author

@arjan arjan commented Aug 3, 2014

I am using relx for packaging. Relx figures the dependency graph out 'automagically' by recursively looking at the .app files, requiring (ideally) no reltool config or other configuration files. And I noticed it didn't pick up bear until I added it to the .app.src.

@rlipscombe
Copy link

@rlipscombe rlipscombe commented Aug 13, 2014

I had to do the same; it's worth pointing out that if you're using folsomite, that forgets to mention protobuffs.

@joewilliams
Copy link
Contributor

@joewilliams joewilliams commented Oct 10, 2014

With bear as an app dependency (and bear not being an application) how are all of you running the eunit tests and etc and succeeding?

1> folsom:start().
{error,{not_started,bear}}
@joewilliams
Copy link
Contributor

@joewilliams joewilliams commented Oct 15, 2014

Fixed in #86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.