[erlang-questions] how do you build your releases with/without rebar?

[Michael Truog]

If you need "rebar generate" behavior in a way that doesn't have extra checks blocking its success and is able to report errors (problems rebar has had in the past), without the logic for windows support, there is a script here:
https://github.com/okeuday/reltool_util/blob/master/release

However, relx should be a better way to go, if you can part with your reltool file.  I haven't found all the reltool options to be supported by relx, so I don't believe it is a fit for all situations.

On 04/10/2014 12:18 AM, Benoit Chesneau wrote:
> Hi all,
>
> I would like to rework the way I am building releases and find a good way to handle the inclusion of dependencies in them. I am generally using the easy path for now by mostly using rebar to get the dependencies but I wonder what others are doing.
>
> How do you get the dependencies, build them and adding them to the release? Are you using your own scripts? Using a makefile like some? In that case how do you maintain the dependencies list and their upgrades?
>
> Any feedback is appreciated :)
>
> - benoit
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140410/3c42b56f/attachment.htm>