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

Core library should not depend on symfony/console #134

Closed
l0c0luke opened this issue Aug 15, 2016 · 9 comments
Closed

Core library should not depend on symfony/console #134

l0c0luke opened this issue Aug 15, 2016 · 9 comments

Comments

@l0c0luke
Copy link

No description provided.

@sidkshatriya
Copy link
Contributor

sidkshatriya commented Aug 17, 2016

The version requirement is ^2.7.0 which means that any version >= 2.7.0 and <= 3.0.0 should work.

Sorry there are no plans to support symfony/console >= 3.0.0 at the moment. Version 3.0.0 and higher change the compatibility requirement with the current code base (basically the amp-console command line utility). Note: The rest of the library does not care about symfony/console at all.

Drupal is also not on symfony 3.0.0 (and higher) last I checked. (Many people use this library from Drupal -- see https://www.drupal.org/project/amp).

It probably could be possible to remove the requirement for symfony/composer all together if you're simply using the library portion only. Then the console can use any symfony version and not affect anything else.

@edubuc
Copy link

edubuc commented Aug 24, 2016

I tried to use the library with Laravel 5.2 but I'm stuck too as it use symfony/console 3.0.9

Any tips on how I can use it anyway? (it will save me a lot of time)

Thanks

@yaquawa
Copy link

yaquawa commented Sep 5, 2016

Yeah, same issue here with Laravel 5.3.
Would you consider separating the console part out from the library?

@sidkshatriya
Copy link
Contributor

Ok I'll see how much work this change might entail.

@yaquawa
Copy link

yaquawa commented Sep 6, 2016

Thanks sidkshatriya!!

@edubuc
Copy link

edubuc commented Sep 6, 2016

Thanks sidkshatriya

@sidkshatriya
Copy link
Contributor

sidkshatriya commented Sep 10, 2016

@yaquawa @edubuc @l0c0luke

I think I've solved it. The solution was almost trivial (and obvious) in retrospect (see PR above). Before I merge to master / create a 1.0.x tag could any of you try it out?

In your project you can either do a:
composer require lullabot/amp:"dev-no-console-dep"

or change the verson constraint for lullabot/amp in composer.json from (probably) "^1.0.0" to "dev-non-console-dep" followed by composer update

One this is confirmed to be OK I'll merge to master. (Subsequently you'll go back to version constraint "^1.0.0" -- so this is just for temporary testing purposes)

The change is on git branch no-console-dep. Composer refers to it as dev-no-console-dep

Also checkout https://packagist.org/packages/lullabot/amp#dev-no-console-dep

@FuzzyTree
Copy link
Contributor

@sidkshatriya composer require lullabot/amp:"dev-no-console-dep" worked for me. Thanks!

@sidkshatriya sidkshatriya changed the title Is the symfony/console 2.7 requirement firm? Stuck trying to upgrade to Smfony 3.1 Core library should not depend on symfony/console Sep 14, 2016
@sidkshatriya
Copy link
Contributor

Thanks @FuzzyTree for testing this out. Merged to master, created tag 1.0.7

no-console-dep branch deleted as this is on master / 1.0.7 tag.

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

5 participants