ligo/scripts/install_build_deps.raw.sh

#! /bin/sh

script_dir="$(cd "$(dirname "$0")" && echo "$(pwd -P)/")"
src_dir="$(dirname "$script_dir")"

. "$script_dir"/version.sh

opams=$(find "$src_dir/vendors" "$src_dir/src" -name \*.opam -print)

opam install $opams --deps-only --with-test -y --criteria="-notuptodate,-changed,-removed"
Opam: use pinned repo in docker image 2018-06-27 14:58:06 +04:00			`#! /bin/sh`

			`script_dir="$(cd "$(dirname "$0")" && echo "$(pwd -P)/")"`
			`src_dir="$(dirname "$script_dir")"`

			`. "$script_dir"/version.sh`

Makefile: no need to pin local packages 2018-07-24 20:11:18 +04:00			`opams=$(find "$src_dir/vendors" "$src_dir/src" -name \*.opam -print)`
Opam: use pinned repo in docker image 2018-06-27 14:58:06 +04:00
Improve make build-deps after a tezos-opam-repository update First this patch makes build-deps non interactive as it should be. More importantly, it changes the optimization problem sent to the opam solver (and that may be a big deal). By default the criteria is `-removed,-changed,-notuptodate`. -changed is problematic because it means that if a dependency has been updated in tezos-opam-repository but all tezos packages are fine with the one currently installed, it is not changed (but as we observe now there might still be in fact packages with undeclared incompatible with this old version)! -remove is also problematic because what we would like to say is "minimize the number of removed 'root' packages" we don't care to remove packages automatically installed and not necessary anymore (especially when they don't compile anymore with updated version of their deps...) So... I reversed order in the criteria. I'm sure this is what I want when the opam switch contains only tezos-opam-repository but unexpected upgrades occur for devs that have done a `opam repo add default --rank=-1`... 2019-01-25 15:04:26 +04:00			`opam install $opams --deps-only --with-test -y --criteria="-notuptodate,-changed,-removed"`