twitter/bower — pull request #103 by satazor (2012-10-23 00:53:21+00:00)
Title: Fix update command in some edge cases

The basis of the update command is to get the local packages, extract their URLs and call the install command with the extracted URLs.

This causes issues because those URLs will be processed by resolveEndpoints in the Manager which will guess the package name from the URL. If the package name does not match the one declared in the URL, weird things happen. One case in which this is happening is the `has` package which is registered in the bower registry but their Git URL is has.js (note the trailing .js).
The install command would create a has folder but the update command would create an has.js folder.

This PR proposes a fix for this issue.