Closed pborreli closed 11 years ago
Silex is dependant on 2.1.*, so it's probably not recommended, but you could give it a try by using a Require Inline Alias in composer? Even if this doesn't work, I'd still consider this ticket a non-issue until Silex moves on to the next version of Symfony.
Perhaps we could have a ticket requesting a tagged release of silex, and then move the master branch on to 2.2?
@davedevelopment : as Symfony 2.2 components are dev versions, >=2.1,<2.3-dev
would allow people like @pborreli to grab the latest component versions by setting the minimum-stability to dev on their project, while it would still require 2.1.* by default for other people.
Indeed, we could even change the constraint to something along the lines of >=2.1,<3.0-dev
.
Just curious, which features from 2.2 are you using?
@bamarni @igorw good points :)
@igorw I'm using the new Progress helper from symfony/console
I'm not confident in making myself a PR as i don't have any way to test the packagist/composer setup. ping @igorw
@igorw for now, I would suggest >=2.1,<2.3-dev
. Putting 3.0-dev
as upper bound would be true if we were sure about the BC. But until 2.3 is released, some BC breaks can still occur sometimes.
thanks !
when I change version of Symfony Components in composer.json of my Silex application (created with create-project fabpot/silex-skeleton) composer can't upgrade them :
I'd like to be able to use 2.2.* or maybe master version of the components, how can I do ?