Installation Failed about jigsaw

[adamwathan]

Sounds like you have some existing globally installed Composer packages that have a conflicting dependency. The annoying thing with globally installed Composer packages is they all live in the same composer.json, so it's very easy to run into conflicts.

The best solution in your case would be to install Jigsaw locally per project to avoid conflicts.

You can do that by creating a new directory for your project and changing to it:

mkdir my-jigsaw-site && cd my-jigsaw-site

...then using Composer to install Jigsaw locally to that folder:

composer require tightenco/jigsaw

Finally, initialize the default project structure:

./vendor/bin/jigsaw init

We've got documentation for this situation on the installation page, under the "Installing Locally" heading:

http://jigsaw.tighten.co/docs/installation/

[ajhaining]

I had the latest version on symfony/console (v3.0.4) already installed.

Fixed by adding "tightenco/jigsaw": "^0.5.0" to my global composer.json and running composer global update.

Possible fix to the jigsaw composer.json by allowing a range of versions up to 3.0.*, if indeed that version of symphony/console fits the requirements?

[adamwathan]

Yeah I don't know for sure that symfony/console: ^3.0 is compatible with Jigsaw unfortunately, will have to see what the breaking changes were.

I'm surprised that fixed it, it must have uninstalled the old version of symfony/console when you did the global update? Must not have actually needed ^3.0 for whatever else you had 👍

[ajhaining]

Yeah it did, the only other thing was Laravel installer which is 2.3 and up.

Just had a play around with Jigsaw, it's brilliant. Good work.

[adamwathan]

Awesome! Thanks @AndrewHaining :)