| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
Instead fetching and resolving src deps (which could depend on pkg deps)
and then pkg deps this patch combines the two into a single set of
iterations by level. The only difference between src and pkg deps in this
new install_deps is how their deps list is found -- from the config or
lock file for src deps and from the neighbors of the vertex for pkg.
|
| | |
|
| |
|
|
| |
Just rework the error message.
|
| |
|
|
|
| |
On a single app's dep list, the first noted wins if there's a duplicate
between packages and sources, rather than favoring source there anyway.
|
| |
|
|
|
| |
Requires a rework of other test suites using the same dep-handling
mechanism.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Should fix #360
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When fetching dependencies for the first time using a profile (`rebar3
as prod release` or `rebar3 ct`), the dependencies get fetched into the
non-default profile. This has two consequences:
- the files get re-downloaded on follow-up runs
- the lock file includes incomplete or too many deps in its list
This patch forces dependencies in the default profile to be stored in
_build/default/lib even when running under other profiles, then symlinks
them to the correct one.
This makes it so common dependencies in 'default' be downloaded there
and avoids re-downloading them. Should also fix the lock issues.
|
| |
|
|
|
|
|
|
| |
The option {deps_error_on_conflict, true} will make it so conflicts in
deps being fetched interrupts the operation rather than just display a
warning.
Defaults to `false'.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
