Closed tonydewan closed 6 years ago
:+1: but it is called script/setup
@janxious I also saw the composer.lock
changes, but it doesn't seem reasonable for this change to have caused that to happen, so I didn't commit it. My (perhaps faulty) assumption is that we need to be more explicit about the versions of some of the dependencies. What do you think?
I had not run the tests before, but I do get a bunch of failures after running them. The same failures happen in master
as well. I wonder if the dependency version changes caused this breakage?
@janxious I reset my local repo and ran script/setup
but removed the last line (composer update
). That stops the dependency updating which prevents the composer.lock
file from changing. The tests still fail, though.
It seems like we shouldn't be updating dependencies every time someone runs script/setup
. What do you think?
It seems like we shouldn't be updating dependencies every time someone runs script/setup. What do you think?
I agree, but also it doesn't seem to be the problem. I also think if we never update dependencies that is also bad.
I agree, but also it doesn't seem to be the problem.
We are aligned. :)
I propose we update this PR to remove the composer update
line and investigate the test failures separately.
Closing in favor of #4 which removes some things but which still does composer update.
script/setup
fails because homebrew doesn't know about the PHP70 brew. We need to tap the relevant repository to make it findable.