rebar.config.sample: fix raw dep example formatting

This commit is contained in:
Tuncer Ayaz 2012-11-14 23:19:42 +01:00
parent e6ee469c4d
commit 9ac9d935c0

View file

@ -139,16 +139,19 @@
{application_name, "1.0.*"}, {application_name, "1.0.*"},
{application_name, "1.0.*", {application_name, "1.0.*",
{git, "git://github.com/basho/rebar.git", {branch, "master"}}}, {git, "git://github.com/basho/rebar.git", {branch, "master"}}},
%% Dependencies can be marked as 'raw'. Rebar does not require
%% Dependencies can be marked as 'raw'. Rebar does not require such dependencies %% such dependencies to have a standard Erlang/OTP layout
%% to have a standard Erlang/OTP layout which assumes the presence of either %% which assumes the presence of either
%% "src/dependency_name.app.src" or "ebin/dependency_name.app" files. %% "src/dependency_name.app.src" or "ebin/dependency_name.app"
%% %% files.
%% 'raw' dependencies can still contain 'rebar.config' and even can have the %%
%% proper OTP directory layout, but they won't be compiled. %% 'raw' dependencies can still contain 'rebar.config' and
%% %% even can have the proper OTP directory layout, but they
%% Only a subset of rebar commands will be executed on the 'raw' subdirectories: %% won't be compiled.
%% get-deps, update-deps, check-deps, list-deps and delete-deps. %%
%% Only a subset of rebar commands will be executed on the
%% 'raw' subdirectories: get-deps, update-deps, check-deps,
%% list-deps and delete-deps.
{application_name, "", {application_name, "",
{git, "git://github.com/basho/rebar.git", {branch, "master"}}, {git, "git://github.com/basho/rebar.git", {branch, "master"}},
[raw]}]}. [raw]}]}.