[erlang-questions] Non-Erlang dependencies

[Roberto Aloi]

In the past, I've added bootstrap as a GIT Submodule and I simply
included it in the release.
This approach didn't work out too well (submodules can be painful).
In the end, I've decided to go for the simple route and to add the
bootstrap files to the repo.
A bit of duplication there, but a lot of simplicity.

@dva: Having a bash script which gets and builds stuff assumes that
you have (Internet) access to the resources you have to build at
building time. Sometimes, that's not the case.

R

On Thu, Jun 28, 2012 at 10:00 AM, Loïc Hoguin <essen@REDACTED> wrote:
> Hey,
>
> I was wondering how you guys currently handle non-Erlang project
> dependencies, with regards to simple development but also releases handling.
>
> For example if you are writing a web application you are certainly going to
> depend on something like jquery+bootstrap. Do you simply put them in your
> own repos? Can't use rebar for this (yet) but maybe you use a nifty trick?
>
> Another example would be a C application that you communicate with through
> ports.
>
> Any feedback welcome, thanks.
>
> --
> Loïc Hoguin
> Erlang Cowboy
> Nine Nines
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions



-- 
Roberto Aloi
---
Website: http://roberto-aloi.com
Twitter: @robertoaloi