Filing a ticket may be a good idea :)
On Thu, Jul 10, 2014 at 4:13 PM, Cameron Junge macro...@gmail.com wrote:
No, as it was a fresh checkout from Git with no vendors installed.
The same playbook runs perfectly on Linux, but fails on OSX.
On Thursday, 10 July 2014 07:32:43 UTC+12,
composer_dir is the location of the composer.json file. There is no
composer.phar at that location as I'm relying on it being installed
system-wide.
If it's something to do with how composer was installed, it was done using
Homebrew, and the module itself finds the location of the
No, as it was a fresh checkout from Git with no vendors installed.
The same playbook runs perfectly on Linux, but fails on OSX.
On Thursday, 10 July 2014 07:32:43 UTC+12, Michael DeHaan wrote:
Changed false seems to imply it did not think it needed to install
anything, because it already was
What is composer_dir?
I have a feeling you are pointing to the wrong file (as in not the real
phar file). The real phar looks like it's on your system at
/usr/local/Cellar/composer/1.0.0-alpha8/libexec/composer.phar
On Tuesday, 8 July 2014 19:48:44 UTC-7, Cameron Junge wrote:
Hi All,
I
