Help to easily make projects based on rebar (like rebar + lot of specific templates).
Just change the .app file and the macro APP with the name of the new application and bootstrap will generate your project.
On top of your changes, you need to rename ebin/rebar.app to rebar/NEW_NAME.app and make sure that the app definition in ebin/NEW_NAME.app uses NEW_NAME.
That said, I don't have a strong opinion on this, but is it crucial to have a different name than rebar for the binary, or would it work to just extend priv/templates before building rebar? Also, I suppose putting the templates in ~/.rebar/templates or in the local project doesn't solve your problem.
Thanks for your quick answer.
Extend priv/templates works well, but when you distribute a single file with a lot of specific stuff inside, it's essential that the user can differentiate it.
Rebar name as a macro, for easy change
Fix bootstrap for easy name change
Why do you not use rebar as a dependency instead of doing this, which seems pretty convoluted.
I'm also wondering why this cannot be a dependency. I'm not super happy about the prospect of having multiple rebar-equivalents-just-with-different-names around. Is there a thing that keeps you from using it as a dependency?
I'll mark this as question for now, and if we don't have an answer within something like 2 weeks (because maybe vacations and whatnot during this summer), we'll be closing this.
Someone knows why R14 can't find include file "include/rebar.hrl" ?
Rebar is a fantastic tool and the erlang standard to dependancies.
As rebar is great for template generation, it should be the de facto standard tool for web frameworks.
BUT, the best erlang web developer drops rebar for some ugly Makefile:
Rebar is the great tool, I just want an easier way to do it..
Really ? DRY.
Don't be afraid of rebar being used ! With my proposition, as everybody will use rebar, all features wil be integrated upstream (i.e. rebar). Without it, real forks with different features will be create.
Does this issue still apply or can we close it? I guess now with rebar3's plugin architecture this doesn't make sense anymore
Yeah I'm not sure it does either. Will close for now.