CocoaPods Trunk about async HOT 17 CLOSED

Hmm, bummer. It's kinda sad to need to change the filename to AsyncSwift.podspec.

Does anyone have any ideas that does require name change?

As a current workaround use pod 'Async', :git => 'https://github.com/duemunk/Async.git'

from async.

There is a claims form for CocoaPods but that's more for libraries that were submitted by other users that the developer wants to claim. In this case maybe talking to @johnwana to change his pod instead?

from async.

Yeah, no. @johnwana's repo is a pure valid use of CocoaPods. It's unfortunate that CocoaPods don't allow to push to trunk with a different name IMO.

from async.

seem that the trunk wasn't pushed?

from async.

@todaylover ??

from async.

the filename has been decided? ah. you can make a decision

from async.

I expect that most developers maintain their own Specs repo, and all that is required is to add an Async directory structure to that.

There is one issue at the moment, and that is a missing remote tag for 1.2.0 so the current podspec is not valid.

from async.

So, How can I install this Async from CocoaPods?
I placed pod 'Async' in Podfile but then it installed https://github.com/johnwana/Async instead of this Async.

from async.

@0angelic0 you can great your own Specs repo, and put Async in it like this, for example: https://github.com/yakatak/Specs/tree/master/Async/1.2.0

Then add this repo to your Podfile e.g.

source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/<< your github name >>/Specs.git'

Then you can use:

pod 'Async'

And CocoaPods will "override" the Async which is in the Master repo. If you wanted to use both, then name changes need to happen. I guess this is what @duemunk will probably have to do in the long run if he wants to submit Async to the trunk.

n.b. Don't use someone else personal Specs repo - create and maintain your own.

from async.

@danthorpe Thanks! I followed your guide and it worked.

from async.

I might have misunderstood something, but why not just use pod 'Async', :git => 'https://github.com/duemunk/Async.git' ?

from async.

@duemunk @0angelic0 yes, this will work if you want to use Async in an application. But it won't work if you want to use it inside an internal framework/dependency.

from async.

Ah, ok. That makes sense. I think the only solution is to call CocoaPods part of the project AsyncSwift.
It would be ok to keep class Async right?

from async.

Absolutely, the class name doesn't need to change. It's just a CocoaPods namespacing issue.

from async.

Renaming the pod to AsyncSwift would be really helpful. It would allow this project to be used as a podspec dependency.

from async.

I've changed the CocoaPods name to AsyncSwift now and pushed to the trunk. Hopefully this works.

from async.

That was quick. Thanks. 👍

from async.