From 2791e57930fad30b5a3616a97a7ad75a99d29c0e Mon Sep 17 00:00:00 2001 From: Beau Simensen Date: Tue, 20 Dec 2011 12:09:16 -0600 Subject: [PATCH] Updated lockfile message for "composer install" command The behaviour of the lockfile was a little confusing to me. I assumed if I added a new dependency I should run 'composer install' again. It was not immediately obvious from the output of the install command what was going on and I was confused why my new package had not been installed. I understand that a better fix would be to compare composer.json to the lockfile, but until that has been implemented this will maybe help some newbies out. --- src/Composer/Command/InstallCommand.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Composer/Command/InstallCommand.php b/src/Composer/Command/InstallCommand.php index 19892fa72..0cded236d 100644 --- a/src/Composer/Command/InstallCommand.php +++ b/src/Composer/Command/InstallCommand.php @@ -108,7 +108,7 @@ EOT $request->install($link->getTarget(), $link->getConstraint()); } } elseif ($composer->getLocker()->isLocked()) { - $output->writeln('Found lockfile. Reading.'); + $output->writeln('Installing from lockfile. (Run "composer update" to add or update packages)'); foreach ($composer->getLocker()->getLockedPackages() as $package) { $constraint = new VersionConstraint('=', $package->getVersion());