<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 10, 2014 at 11:05 AM, Michael Truog <span dir="ltr"><<a href="mailto:mjtruog@gmail.com" target="_blank">mjtruog@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>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:<br>
<a href="https://github.com/okeuday/reltool_util/blob/master/release" target="_blank">https://github.com/okeuday/reltool_util/blob/master/release</a><br>
<br>
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.<div><div class="h5"><br></div></div></div></div></blockquote><div><br></div><div>But how do you manage the dependencies?</div><div><br></div><div>In a rebar world you're doing:</div><div><br></div><div>
1. rebar get-deps</div><div>2. rebar compile which build deps and what you have in subdirs</div><div>3. rebar generate which reuses what you fetched in deps etc.</div><div><br></div><div>Using <a href="http://erlang.mk">erlang.mk</a>:</div>
<div><br></div><div>1. fetch the dependeinces using curl and some links you have in a file or such thing</div><div>2. compile, but not sure if every apps in apps/* are compiled</div><div>3. use relx or anything else to buld the relese</div>
<div><br></div><div>You can also have 1 make file per app etc.</div><div><br></div><div>I am curious how people manage to get the dependencies without rebar or <a href="http://erlang.mk">erlang.mk</a>, build them and then tell to reltools or relx where to find to include them in the release.</div>
<div><br></div><div>IN cloudi it seems for examle that you're using rebar for that. but I can see some projects around publishing their app without any support for rebar. How is it handled behind?</div><div><br></div>
<div>- benoit</div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><div><div class="h5">
<br>
On 04/10/2014 12:18 AM, Benoit Chesneau wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>Any feedback is appreciated :)</div>
<div><br>
</div>
<div>- benoit</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><div class=""><pre>_______________________________________________
erlang-questions mailing list
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</div></blockquote>
<br>
</div>
</blockquote></div><br></div></div>