Composer versions mismatch when creating skeleton project

[lferro9000]

When trying to setup PSR7-Sessions just after creating a new skeleton project, the dependencies installed are not compatible between them.

One has to perform a composer update before installing it (as documented in):

psr7-sessions/storageless#47

This is not a big deal, but should either be corrected on the command level or documents on the instalation guides to avoid new developers getting stuck with composer issues.

Cheers,
LF

[Ocramius]

To clarify what is going on here: the composer.json and composer.lock don't correspond. Running a composer update after running the expressive installer causes some changes in the environment. This is because the installer config.php is just copied to composer.json.

In general, this means that the composer execution is modified with packages that don't correspond the current composer.json execution, causing (for example) ocramius/proxy-manager:2.0.1 to be installed, while ocramius/proxy-manager:^1.0 is written to the composer.json

[Ocramius]

Note that composer doesn't reload the composer.json contents after a pre-install-cmd or a pre-update-cmd: that's the actual problem.

[geerteltink]

@Ocramius Is there anyway composer can be forced to reload the composer.json file that you know of?

[Ocramius]

Not as far as I know.
On Mar 13, 2016 7:52 AM, "Geert Eltink" notifications@github.com wrote:

@Ocramius https://github.com/Ocramius Is there anyway composer can be
forced to reload the composer.json file that you know of?

—
Reply to this email directly or view it on GitHub
#79 (comment)
.

[geerteltink]

@Ocramius The actual problem was that the version constrain was never set for an added package. That caused composer to load the latest available package, even if it was a higher version than the actual required version string.