GitHub CocoaPods conflict with CocoaPod Repository Pods

Question

Viewing: https://guides.cocoapods.org/using/the-podfile.html

I finally figured out that my CocoaPods project name that I get from "git lib create" isn't guaranteed to be the same once it's eventually added to the CocoaPod repository.

I was testing my podspec dependency, and tried my repository name. I got a lot of code but not mine: KSFramework.

s.dependency 'KSFramework'

But since the following syntax isn't allowed, is the only way to test a Pod dependency via the installed CocoaPod repository?

ERROR: s.dependency 'KSFramework', :git => 'https://github.com/ME/KSFramework'

This is confusing as the s.source specifies a git repository, but other than Podfile specification, the only repositories available are from the CocoaPods, and not my GitHub files.

 s.source = { :git => 'https://github.com/ME/KSFrameworkVersionTest.git', :tag => s.version.to_s }

I've been looking at various issues between the private Pods (on my computer), the git hosted Pods, and eventually the CocoaPod hosted Pods.

Can someone clarify these issues? thanks.

one reference: How does CocoaPods work

• Paul Beusterien: See guides.cocoapods.org/making/making-a-cocoapod.html
• KonaCurrents: The manual doesn't explain that private pods and git hosted pods can't be used in Pod development dependencies; only those pushed to the CocoaPods repository. I don't see how these constraint will allow much private or team development. Yes, I know the Podfile can specify all this, but that is the end use of Pods, not the Pod development. Thanks.
• KonaCurrents: private pod dependency sums up my question as others would like to add their private repository as a dependency for another private pod. Also the private pods doesn't show this either. So again, if private pod dependency isn't available it really limits capability. thanks.