Rebar problem summary

1. {lib_dirs, ["path1", "path2"]}, specify multiple scan root directories of the dependent package. The default value is the "deps" directory under the current application, modify the "deps" Directory through {deps_dir, "person_deps_path "};
2. dependency Description: A-> B; B-> C; application C does not need to put application B in the deps directory of application C, you can put both B and C in the deps directory of application;
3. the corresponding 2nd rules can be established because a only looks for dependencies in its own deps directory and does not recursively look for dependencies in B's deps directory. (This problem seems to be wrong, rebar can be recursive, not a layer)
4. Some options of the release application's reltool. config configuration file are described as follows:
1. {lib_dirs, [".../"]} is the application path, and "relative path" is the path of this file ".
2. {Rel,...} is the number of services contained in the application, which is automatically started when the system is running.