问题描述
我正在同时开发一个私人cocoapod，并同时使用该cocoapod，但是我在确定正确的工作流程以保持所有内容同步方面遇到困难。
I'm working on a private cocoapod and project using that cocoapod concurrently, and I'm having difficulty settling on the right workflow for keeping everything synchronized.
我遇到的问题是：如果我对cocoapod项目进行了更改，我发现让我的其他项目进行这些更改的唯一方法是创建新标签并更改Pod引用的版本规格结果，我陷入了很多无用的Pod规范版本中。
The problem i am encountering is this: If i make a change to my cocoapod project, I've found that the only way I can get my other project to pull those changes is if I create a new tag and change the version referenced by the pod spec. As a result, I'm getting stuck with many useless versions of my pod spec.
我希望将标签简单地移动到cocoapod项目的头然后以某种方式重新拉起椰壳足我发现在这种情况下，pod的安装和更新似乎并没有刷新cocoapod。
What I would prefer is to simply move my tag to the head of my cocoapod project and somehow re-pull the cocoapod. I've found that pod install and pod update do not seem to refresh the cocoapod in this circumstance.
有人对同时开发cocoapod和项目有任何建议吗？
Does anyone have any recommendations for concurrently working on a cocoapod and a project that uses it?
推荐答案
您还可以使用：head 标志但您仍必须创建标签。
You could also use the :head flag but you would still have to create the tags.
pod 'YourPod', :head
运行 pod update 时，会使用pod的最新版本规范。
When running pod update the pod’s latest version spec would be used.
这篇关于强制使用相同标签更新Cocoapod的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！