missing app file
watson.timothy at gmail.com
Fri Oct 28 13:09:28 EDT 2011
On 28 October 2011 17:53, David Smith <dizzyd at basho.com> wrote:
> On Fri, Oct 28, 2011 at 10:48 AM, Joel Reymont <joelr1 at gmail.com> wrote:
> > Using apps then makes it impossible to use ejabberd as a dependency
> because rebar does not look under deps/<App>/apps/.
> If you want a composition of deps, you need to break the apps into
> individual repos.
> Combining multiple erlang apps into a single repo is a way of
> indicating that they move in lockstep and are a top-level
> package/release of apps. It shouldn't _be_ a dependency of anything
This makes perfect sense, and yet I can think of a dozen uses for ejabberd
or rabbitmq or whatever, where the top-level thing is just a part of the
whole. It would be better for ejabberd to be packaged in such a way that you
can use it either as a top level thing or as one of several component
applications required by a release. But clearly not everyone does this and
it's a big overhead to keep on forking projects like ejabberd just to
maintain a different directory structure and configuration.
I'm not suggesting rebar should handle this BTW, quite the opposite. If Joel
can get processone to integrate a rebarized configuration then great,
otherwise IMO the best thing is to use plugins to customise this kind of
"special case" and accept it as an annoyance.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rebar