CocoaPods/CocoaPods — pull request #338 by subdigital (2012-06-14 20:48:17+00:00)
Title: Better error msg for missing podspec

First checks the project's root for a .podspec,
Then goes on to check the Local Pods folder,
if that can't be found raises an informative error.

Currently this breaks a couple of tests, as the behavior for `sandbox#podspec_for_name(name)` of returning nil apparently is being depended on. Submitting a pull request to begin the discussion.

Do you think this is the right approach?

The tests that are broken:

**`Pod::Resolver`**
- holds the context state, such as cached specification sets [FAILED]
- returns all specs needed for the dependency [FAILED]

**`Pod::Command::Spec::Linter`**
- uses xcodebuild to generate notes and warnings [FAILED]
- checks for file patterns [FAILED]

If you think this is the right approach, I'll look at how to fix these specs to not depend on a `nil` return value from that method.