Closed mrkrstphr closed 9 years ago
This is an interesting Composer problem and I'm not certain that it is behaving as users might expect. The problem is that requiring a package without a version number defaults to the "most recent stable semantic version." In the case of silex/silex, that is ~1.2. In the case of the ORM provider, that is ~2.0. It looks like it decides on these independent from each other.
The problem is that the 2.0.x version of the ORM provider only works with Silex 2. However, there are no stable versions of silex/silex available for 2.0.x.
You have to decide if you want stable silex ( ~1.2 ) or if you want to use the most recent silex ( ~2.0@dev ). If you want stable silex, then you need to specify an older version of the ORM provider. If you want the mot recent silex, you need to allow for @dev
stability for silex.
# Stable Silex and an older stable version of the ORM provider.
$ composer require silex/silex dflydev/doctrine-orm-service-provider:~1.0
# Unstable version fo Silex and the most recent version of the ORM provider.
$ composer require silex/silex:~2.0@dev dflydev/doctrine-orm-service-provider
That's what I ended up doing to install it. It's a bummer that Composer doesn't figure which stable versions work together for you.
Thanks for the tip!
I can't get this provider to install with Silex:
What am I doing wrong?