composer/composer — Issue #358: Ensure locked source reference when installing a dev-package
Author: perprogramming
Created: 2012-02-23 17:28:10+00:00
State: open

I have a project requiring a package in a dev-version (e.g. "symfony/symfony": "dev-master").

When I "composer update" this project and new changesets of "symfony/symfony" were pushed to the master branch, composer downloads these changesets and writes a new source reference for the package in the lockfile. I then commit the new lockfile to the project to ensure that all colleagues are working with the same version of "symfony/symfony".

But when my colleagues run a "composer install", nothing happens.

As far as I am able to understand the implementation of InstallCommand this is to expected because an install operation for a package is only executed when it is part of the resolvers solution. As the solver does not now about source references and the package is already in version "dev-master" on my colleagues machine, the solver returns with no operation.

Is this a missing feature or am I still misunderstanding the lockfile? ;)