[erlang-questions] best source layout with multiple applications

[Sergej Jurečko]

Use the riak way of doing things. That way rebar and node_package will work
well when creating a release. Diverge too far from that and you're likely
to run into issues later on.


Sergej


On Mon, Jan 6, 2014 at 2:30 PM, Fred Hebert <mononcqc@REDACTED> wrote:

> I personally tend to follow the Riak structure and recommend it around
> for releases instead of having one top-level app and then the rest below
> it. I'd be open to using lib/ instead of /apps, but feel like deps/ is
> the best name for dependencies of the project (which aren't always about
> other vendors or even third party libraries -- just stuff generic enough
> to not be in the core project).
>
>
> Regards,
> Fred.
>
> On 01/06, Benoit Chesneau wrote:
> > Hi all,
> >
> > I am wondering what would be the best layout to handle multiple
> > applications in the same repository and their dependencies? I am using
> > rebar to handle the build of the apps and the C code they are using.
> >
> >
> > When I see around I can see the following layouts:
> >
> > riak is using
> >
> >  - apps/app1
> >    ...
> >    apps/appN for apps
> >
> > - deps/ for the defaults
> >
> >
> > cloudi :
> >
> >  - src/lib/app1
> >    ...
> >    src/lib/appN for cloudi apps
> >
> > - src/external/... for deps included
> >
> > Erlang
> >
> > - lib/app1...appN for apps
> >
> >
> > I am myself thinking to use
> >
> > - lib/app1....appN for apps
> > - vendor/.... for deps
> >
> > maybe under an src/ folder.
> >
> >
> > But I am curious of what others do. Any feedback is welcome :)
> >
> > - benoit
>
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> 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/20140106/3b084314/attachment.htm>