Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

php-parser 2.x #79

Open
aleksanderd opened this issue Jun 6, 2016 · 3 comments
Open

php-parser 2.x #79

aleksanderd opened this issue Jun 6, 2016 · 3 comments

Comments

@aleksanderd
Copy link

Hi!

I have an error while installing php7cc:

./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.044 seconds
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for sstalle/php7cc ^1.1 -> satisfiable by sstalle/php7cc[1.1.0].
    - Conclusion: remove nikic/php-parser v2.1.0
    - Conclusion: don't install nikic/php-parser v2.1.0
    - sstalle/php7cc 1.1.0 requires nikic/php-parser ~1.4 -> satisfiable by nikic/php-parser[v1.4.0, v1.4.1].
    - Can only install one of: nikic/php-parser[v1.4.0, v2.1.0].
    - Can only install one of: nikic/php-parser[v1.4.1, v2.1.0].
    - Installation request for nikic/php-parser (locked at v2.1.0) -> satisfiable by nikic/php-parser[v2.1.0].


Installation failed, reverting ./composer.json to its original content.

It is cos I already have installed php-parser 2.1.0 required by drush.
What the best way to resolve the problem? Is it really needed to require php-parser v1.4 for php7cc or v2.x is ok too?

Thank you!

@sstalle
Copy link
Owner

sstalle commented Jun 6, 2016

Hello, @aleksanderd. I think php7cc will not work with PHP-Parser 2.x because of backwards incompatible changes introduced in 2.0. The code will have to be updated to make it work. I don't have an exact ETA right now, but I'll try to do it in the following month. Until then, I don't really see a good way to resolve your problem besides using one of the prebuilt phar packages from the releases page.

@aleksanderd
Copy link
Author

Huge thnx!
phar package is enough solution, I think.

@veewee
Copy link

veewee commented Oct 26, 2016

Hi @sstalle,

Thanks for your package! Any update on the upgrade to ~2.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants