🌈
(Previously discussed somewhat in issue #4636.)
I believe that this is an intentional change, but I think there are valid use cases for wanting to use the deployment target of the app/target, which is sometimes higher. My use case is conditionally compiling code depending on the deployment target. You can remove unnecessary code, dependencies, or workarounds this way. Perhaps there should be an option in the Podfile and/or Podspec to opt-in to this behavior.
(By the way, there's no way to specify in a Podspec that a dependency should only be included if the deployment target is below a given version, right? For example, JSONKit if < iOS 5.)
🌈
(Previously discussed somewhat in issue #4636.)
I believe that this is an intentional change, but I think there are valid use cases for wanting to use the deployment target of the app/target, which is sometimes higher. My use case is conditionally compiling code depending on the deployment target. You can remove unnecessary code, dependencies, or workarounds this way. Perhaps there should be an option in the Podfile and/or Podspec to opt-in to this behavior.
(By the way, there's no way to specify in a Podspec that a dependency should only be included if the deployment target is below a given version, right? For example, JSONKit if < iOS 5.)