Conversation
dhopkalo
commented
Oct 3, 2017
- update composer.json minimum-stability from stable to dev
- update&sync composer.lock with composer.json
- update composer.json minimum-stability from stable to dev - update&sync composer.lock with composer.json
|
From what I‘ve learned lock files for packages are disregarded by composer anyway and thus should not be committed. As for the stability- does this fix a particular issue you‘re seing? I don‘t think its required here. |
|
I just try to do minimal changes to do independently run php-pm like a tool for projects inside docker container. Try to do next: and see the next problem http://prntscr.com/gt41b6
run composer require again
and see other problem http://prntscr.com/gt43b6 In my case I temporary use php-pm/httpkernel-adapter like a tool and run php-pm from the But if we think about httpkernel-adapter like an independent component we need to stop require I see that you require php-pm to have the next interfaces But you don't need to require it directly from the php-pm, just move it to the abstraction layer(other repo only with interfaces) and require this repo in both packages. |
|
About lock file you are right - when you do 'composer require' on other project he are disregarded. |
|
Please install php-pm and then require php-pm-httpkernel. The other way round will not work. |
|
Is it not interesting to make php-pm to be independent from the application ? I run php-pm installed independent from the application and it works now like php-fpm, that doesn't know anything about application, and to do it possible i require some change of the package deps now. And now the one question that i have. Is php-pm project going to be independent from applications in the feature ? |
|
Should be fixed via php-pm/php-pm#271 |