Dependencies

[barry1955]

I have a quite complicated ( >50 packages) project.
This tends to cause dependency conflicts between packages if and when I need another. THe application is an enterprise location based Campus AM/FM systems.

We have been using apigility for some time. I now need to add doctrine support (to integrate with ZfcUser, ZFCUserLDAP and byjAyuthorize ) and I hit the following conflict.

The section of my composer.json looks like
```
zendframework/zend-loader": "~2.3",
"zendframework/zend-mvc": "~2.3",
"zendframework/zend-modulemanager": "~2.3",
"zendframework/zend-view": "~2.3"
.
....
"require-dev" :
{
"zfcampus/zf-apigility-admin" : ">=1.5.9",
"zfcampus/zf-development-mode" : "~3.1.0",
"zfcampus/zf-apigility-welcome" : "~1.0"
},

The composer update command gives me the following errors:
` Problem 2
    - zfcampus/zf-apigility-welcome 1.0.1 requires zendframework/zend-mvc ~2.3 -> satisfiable by zendframework/zend-mvc[2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.4.0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.4.0rc5, 2.4.0rc6, 2.4.0rc7, 2.4.1, 2.4.10, 2.4.11, 2.4.12, 2.4.13, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.7.0, 2.7.1, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9] but these conflict with your requirements or minimum-stability.
    - zfcampus/zf-apigility-welcome 1.0.0 requires zendframework/zend-mvc ~2.3 -> satisfiable by zendframework/zend-mvc[2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.4.0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.4.0rc5, 2.4.0rc6, 2.4.0rc7, 2.4.1, 2.4.10, 2.4.11, 2.4.12, 2.4.13, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.7.0, 2.7.1, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9] but these conflict with your requirements or minimum-stability.
    - zfcampus/zf-apigility-welcome 1.0.1 requires zendframework/zend-mvc ~2.3 -> satisfiable by zendframework/zend-mvc[2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.4.0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.4.0rc5, 2.4.0rc6, 2.4.0rc7, 2.4.1, 2.4.10, 2.4.11, 2.4.12, 2.4.13, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.7.0, 2.7.1, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9] but these conflict with your requirements or minimum-stability.
    - Installation request for zfcampus/zf-apigility-welcome ~1.0 -> satisfiable by zfcampus/zf-apigility-welcome[1.0.0, 1.0.1].`

Given the large number of packages we are using I'm wondering what the best strategy going forward is. 

I have resolved some similar issues by 

- forking the package
- edit it's composer.json 
-  run composer update
- fix typos (I do a lot of this)
 
Then of course if I hit issue in the code, I'll update the version in my forked copy (haven't had to yet)

I'm relatively new to composer and would really appreciate feedback.
Am I doing the right thing?  
Are there better ways to get the same end result?

[weierophinney]

This repository has been closed and moved to laminas-api-tools/api-tools-welcome; a new issue has been opened at laminas-api-tools/api-tools-welcome#9.