search

qossmic / deprecation-detector

MIT License
391 stars 40 forks source link

Remove unbound version constraint for PHP #118

Closed soullivaneuh closed 8 years ago

soullivaneuh commented 8 years ago

Ref: https://getcomposer.org/doc/faqs/why-are-unbound-version-constraints-a-bad-idea.md

theofidry commented 8 years ago

@Soullivaneuh you should do one as well on Sf, Laravel & co :P

soullivaneuh commented 8 years ago

I'm to shy for that. :trollface:

xabbuh commented 8 years ago

@theofidry @Soullivaneuh Speaking of Symfony we will create patch releases to add support for newer PHP versions (see http://symfony.com/doc/current/contributing/code/maintenance.html).

soullivaneuh commented 8 years ago

Speaking of Symfony we will create patch releases to add support for newer PHP versions

@xabbuh Great, but what about unbound constraint?

Maybe PHP 10 will not be compatible with SF 2.3. But at this point the user can install this version.

Removing the unbound constraint will prevent this case with composer error on update.

xabbuh commented 8 years ago

@Soullivaneuh But at the time of the release of PHP 10, Symfony 2.3 will not be supported anymore for a long time.

soullivaneuh commented 8 years ago

This is exactly why PHP unbound version constraint should be avoided. ;-)

Sullivan SENECHAL

Le 4 juil. 2016 11:17, "Christian Flothmann" notifications@github.com a écrit :

@Soullivaneuh https://github.com/Soullivaneuh But at the time of the release of PHP 10, Symfony 2.3 will not be supported anymore for a long time.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sensiolabs-de/deprecation-detector/pull/118#issuecomment-230244620, or mute the thread https://github.com/notifications/unsubscribe/ABnqNayQ_EThl49-PPdTy2HKv8HdYtilks5qSM-mgaJpZM4JDXP3 .