~/.composer/bin/wp no longer valid?

[brianfeister]

In a Vagrant box I'm starting from fresh install, the SALT config file (which calls curl http://wp-cli.org/installer.sh | bash to install WP-CLI) installs the Vagrant box and then later calls WP-CLI via .composer/bin/wp, which stopped working in the past few weeks (it worked with the original release where I did the install, but something might have changed?). @danielbachhuber might be able to add details, but I wasn't sure if this was a known change (~/.composer/bin/wp --> ~/.wp-cli/bin/wp) but I couldn't find any record of it. At the very least I wanted to document it here in case anyone else has issues with filepath from a Vagrant project or other setup that calls uses curl to install the latest and finds that their bash filepaths have become invalid.

[scribu]

See wp-cli/wp-cli.github.com@270fcf1

[brianfeister]

Thanks @scribu! Sorry I wasn't able to find it before :/

[scribu]

No worries. Also see composer/composer#55 (comment)