summaryrefslogtreecommitdiff
path: root/src/rebar_prv_upgrade.erl
Commit message (Collapse)AuthorAgeFilesLines
* fix pkg name during update by using pkg_name understood by hexAndrás Boroska2018-12-021-2/+4
|
* support for hex v2, multiple repository fetching, private organizations (#1884)Tristan Sloughter2018-09-131-1/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * update to hex_core for hex-v2 repo support (#1865) * update to hex_core for hex-v2 repo support This patch adds only single repo hex-v2 support through hex_core. Packages no longer filtered out by buildtool metadata and the package index is updated per-package instead of fetched as one large ets dump. * tell travis to also build hex_core branch * support list of repos for hex packages (#1866) * support list of repos for hex packages repos are defined under the hex key in rebar configs. They can be defined at the top level of a project or globally, but not in profiles and the repos configured in dependencies are also ignored. Searching for packages involves first checking for a match in the local repo index cache, in the order repos are defined. If not found each repo is checked through the hex api for any known versions of the package and the first repo with a version that fits the constraint is used. * add {repos, replace, []} for overriding the global & default repos * add hex auth handling for repos (#1874) auth token are kept in a hex.config file that is modified by the rebar3 hex plugin. Repo names that have a : separating a parent and child are considered organizations. The parent repo's auth will be included with the child. So an organization named hexpm:rebar3_test will include any hexpm auth tokens found in the rebar3_test organization's configuration. * move packages to top level of of hexpm cache dir (#1876) * move packages to top level of of hexpm cache dir * append organization name to parent's repo_url when parsing repos * only eval config scripts and apply overrides once per app (#1879) * only eval config scripts and apply overrides once per app * move new resource behaviour to rebar_resource_v2 and keep v1 * cleanup use of rebar_resource module and unused functions * cleanup error messages and unused code * when discovering apps support mix packages as unbuilt apps (#1882) * use hex_core tarball unpacking support in pkg resource (#1883) * use hex_core tarball unpacking support in pkg resource * ignore etag if package doesn't exist and delete if checksum fails * add back tests for bad package checksums * improve bad registry checksum error message
* Add hooks to the upgrade commandFred Hebert2018-06-051-0/+13
| | | | As requested in #1733
* Changes word 'transient' to 'transitive' which is what it is supposed to sayJimmy Zöger2017-09-141-1/+1
|
* Unicode support in all the placesFred Hebert2017-08-061-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is done through 3 main change groups: - replacing `~s` by `~ts` in format strings, so that strings that contain unicode are properly printed rather than crashing - adding the `unicode` argument to all function of the `re` module to ensure transformations on strings containing unicode data are valid instead of crashing (see issue #1302) - replacing `ec_cnv:to_binary/1` and `ec_cnv:to_list/1` with matching functions in `rebar_utils`. The last point has been done, rather than modifying and updating erlware commons, because binary and list conversions can be a contentious subject. For example, if what is being handled is actually bytes from a given binary stream, then forcing a byte-oriented interpretation of the data can corrupt it. As such, it does not appear safe to modify erlware commons' conversion functions since it may not be safe for all its users. Instead, rebar3 reimplements a subset of them (only converting atoms and chardata, ignoring numbers) with the explicit purpose of handling unicode string data. Tests were left as unchanged as possible. This may impact the ability to run rebar3's own suites in a unicode path, but respects a principle of least change for such a large patch.
* Cull default dep names in non-default upgradeFred Hebert2017-05-191-10/+28
| | | | | | Prevents showing false upgrade messages when upgrading in a non-default profile. Also shows an info message explaining default deps don't get updated in a non-default upgrade.
* Allow to upgrade profile-specific dependenciesFred Hebert2017-05-071-7/+21
| | | | | | Only happens when calling `rebar3 as <profiles> upgrade <dep>`, with the caveat that all profile deps get upgraded and lined up with the rebar config.
* Fix typo in help text for upgrade commandJuan Facorro2017-03-031-1/+1
|
* Rework patch to work without accidentFred Hebert2016-06-061-5/+21
| | | | | | | The previous iteration of the patch worked somewhat by accident. After digging in and figuring out why the two dep sources are the way they are, the patch is now properly working with a well-documented explanatiion inline.
* Account for umbrella apps' deps in upgradesFred Hebert2016-06-041-1/+7
|
* break up do/1 function in install_deps to make upgrade less confusingTristan Sloughter2016-02-191-1/+1
|
* add test to not upgrade unrelated transitive dep during upgradeTristan Sloughter2015-09-261-1/+1
|
* only upgrade children and transitive children of dep being upgradedTristan Sloughter2015-09-261-19/+43
| | | | | | | | | | This commit replaces the method of upgrading by unlocking all transitive deps by one that utilizes the parent element of each app to only unlock transitive deps of children of the top level deps being upgraded. Additionally the run function of upgrade_SUITE is modified to only create the mock updates before the upgrade provider is run, instead of before any provider is run, which would cause improper behavior in install_deps.
* don't error on upgrade if user removes top level depTristan Sloughter2015-08-231-1/+2
|
* this patch treats pkg and src deps as equals, so level decides winnerTristan Sloughter2015-08-211-2/+1
| | | | | | | | 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.
* track the parent of umbrella app dependenciesTristan Sloughter2015-08-161-7/+10
|
* upgrade depends on the lock provider and lock prv sets stateTristan Sloughter2015-08-021-14/+10
|
* only use upgrade on default depsTristan Sloughter2015-08-011-1/+1
|
* fix upgrade of newly added pkg dep from scm locked depTristan Sloughter2015-07-251-9/+4
|
* Merge pull request #487 from ferd/fix-provider-barenessTristan Sloughter2015-05-301-1/+1
|\ | | | | fix bareness issues
| * fix bareness issuesFred Hebert2015-05-311-1/+1
| | | | | | | | | | | | - Crashes in providers lib when no providers in a namespace are bare - Making sure bareness matches semantics; i.e. a bare provider is visible, a non-bare provider is hidden.
* | Fix upgrade of atom-only packagesFred Hebert2015-05-281-6/+15
|/ | | | they would always be left unfound otherwise.
* on upgrade of git branch check against remoteTristan Sloughter2015-05-031-1/+0
|
* handle transitive deps being promotedFred Hebert2015-04-241-11/+20
|
* use PRV_ERROR for formattable errorsFred Hebert2015-03-161-3/+4
| | | | Also expose it in rebar_api
* Warnings for Deletions and friendly errorsFred Hebert2015-02-121-10/+28
| | | | | | | | | Apps that are no longer used are not automatically deleted, but we tell users it can be done. This is safer while we're not sure of the correctness of these messages. Error messages are added for transient dependencies and dependencies not found.
* Support multiple app upgrade & lock testsFred Hebert2015-02-111-19/+19
| | | | | | - Many apps is supported through and through - Not mentioning any app upgrades all apps - Locks are refreshed on disk and tested as such after an upgrade
* Fix testcases, add multi-app upgrade supportFred Hebert2015-02-111-17/+54
| | | | | | | | todo: - relock stuff - default to all apps needing upgrade - more tests? - pkgs?
* More progress on upgradesFred Hebert2015-02-111-2/+2
| | | | | | Only the most complex case is failing, where cross-dependencies would need to be refetched as an update clears an app of its dependencies and a different subtree should override it.
* Partial work + Failing testsFred Hebert2015-02-111-1/+1
| | | | | The problem with the current effort is handling of transitive dependency upgrades and possible values.
* Alternative attemptFred Hebert2015-02-111-25/+25
|
* WIPFred Hebert2015-02-111-14/+34
| | | | | | Test that all the correct locks are set for an upgrade run. Now to actually re-run the install deps and prove it works
* fixes for dialyzer findingsTristan Sloughter2014-11-301-3/+7
|
* move back to using format_error/1Tristan Sloughter2014-11-091-4/+4
|
* cleanup upgrade packageTristan Sloughter2014-11-021-10/+5
|
* wip: upgrade pkg depsTristan Sloughter2014-11-021-1/+5
|
* add format_error/2 provider callback to providersTristan Sloughter2014-10-221-1/+6
|
* split options up by taskTristan Sloughter2014-10-101-23/+24
|
* move providers to separate appTristan Sloughter2014-10-031-9/+9
|
* add upgrade providerTristan Sloughter2014-09-281-0/+49