• Luke Redpath's avatar
    My earlier Resolver/TargetInstaller refactoring broke the handling of target-specific specs, · fde621d0
    Luke Redpath authored
    because previously each TargetInstaller would resolve it's specs separately.
    
    Instead, we resolve everything in one go as before, but have the resolver return a hash of
    target dependencies to resolved specifications, so when the target installers are run, we only
    install the pods for that target that should be in there.
    
    Likewise, we should only call the post-install hook of a specification with the target installers
    it belongs to.
    fde621d0
Name
Last commit
Last update
bin Loading commit data...
examples Loading commit data...
external Loading commit data...
lib Loading commit data...
spec Loading commit data...
.gitignore Loading commit data...
.gitmodules Loading commit data...
.kick Loading commit data...
.travis.yml Loading commit data...
CHANGELOG.md Loading commit data...
Gemfile Loading commit data...
Gemfile.lock Loading commit data...
Guardfile Loading commit data...
LICENSE Loading commit data...
README.md Loading commit data...
Rakefile Loading commit data...
TODO Loading commit data...
cocoapods.gemspec Loading commit data...
scratch-pad.md Loading commit data...