Add env variable to select bundle in case user has multiple. about cocoapods-app HOT 8 CLOSED

What about User Defaults instead? (Just a suggestion, not sure what's really best)

from cocoapods-app.

@AliSoftware That is an interesting thought! But let’s keep it simple with an env variable for now, until people really start requesting a persistent way to do this.

from cocoapods-app.

Problem with ENV variables is what I explained in Slack the other day: If one want to add a "Script Build Phase" that uses CP to its Xcode project, which is shared among coworkers (where everyone is supposed to have CocoaPods installed on their machine), then per-machine environment variables are not that easy to insert into Xcode's Script Build Phases.

from cocoapods-app.

Everyone should use the same version of :cp:, though, so it makes sense to hard-code it in the script phase.

from cocoapods-app.

@neonichu Except if some prefer to install it in ~/Applications instead of /Applications for example, or if one want to use the gem-installed version and have a different $GEM_HOME that the default one, etc…

from cocoapods-app.

@AliSoftware In our case, assuming that you would call the bundle the same (e.g. CocoaPods-0.35.0.app) it wouldn’t matter where you place it on disk, the pod binstub will find it with env CP_APP=CocoaPods-0.35.0 pod […].

from cocoapods-app.

@AliSoftware those are tangential to the environment variable for the binstub, though.

from cocoapods-app.

After a bit more consideration, I think it makes sense to already add support for reading it from a User Default, but setting it should be done through the defaults command.

from cocoapods-app.