Public PodSpec about openssl HOT 16 CLOSED

I feel you pain.

At the moment (AFAIK) there is no way to specify custom source for fetchable dependency in .podspec file. It have to be specified in Podfile.

AFAIK There is OpenSSL in public repository, if you specify dependency in podspec that one will be used (Have you tried that one?)

from openssl.

Is creating a podspec (with a different name) and publishing it to the
private repository an option?

Tom

On Thu, Jan 9, 2014 at 11:35 AM, Marcin Krzyzanowski <
[email protected]> wrote:

I feel you pain.

At the moment (AFAIK) there is no way to specify custom source for
fetchable dependency in .podspec file. It have to be specified in Podfile.

AFAIK There is OpenSSL in public repository, if you specify dependency in
podspec that one will be used (Have you tried that one?)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-31915077
.

from openssl.

Well then everybody else would need to add that repository first. Thus is bummer.

You can instruct what should be addedd in Podfile.

from openssl.

Why would they have to do that?
All you need to do is give the pod a different name.

Tom

On Fri, Jan 10, 2014 at 5:04 PM, Marcin Krzyzanowski <
[email protected]> wrote:

Well then everybody else would need to add that repository first. Thus is
bummer.

You can instruct what should be addedd in Podfile.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-32034142
.

from openssl.

Yes changed name could reach public repo but... actually I dont have idea how it could be. I think the main difference is that my build is for iOS and OSX

from openssl.

That is quite a big difference. Since you support platforms that are
popular and in use.
Would you like me to do it?

Tom

On Tue, Jan 21, 2014 at 11:31 PM, Marcin Krzyzanowski <
[email protected]> wrote:

Yes changed name could reach public repo but... actually I dont have idea
how it could be. I think the main difference is that my build is for iOS
and OSX

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-32965772
.

from openssl.

sure, but I don't have good idea for new name. OpenSSL is already taken.

from openssl.

How about OpenSSL-iOS/Mac?

Tom

On Thu, Jan 23, 2014 at 12:23 PM, Marcin Krzyzanowski <
[email protected]> wrote:

sure, but I don't have good idea for new name. OpenSSL is already taken.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33112046
.

from openssl.

I think about OpenSSL-Universal

from openssl.

Sounds good!
So are you going to publish?

Tom

On Tue, Jan 28, 2014 at 11:15 AM, Marcin Krzyzanowski <
[email protected]> wrote:

I think about OpenSSL-Universal

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33461826
.

from openssl.

yes, I'm about to push it to Cocoapods

from openssl.

Great. Can you please let me know once its public?

Tom

On Tue, Jan 28, 2014 at 1:15 PM, Marcin Krzyzanowski <
[email protected]> wrote:

yes, I'm about to push it to Cocoapods

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33469593
.

from openssl.

CocoaPods/Specs#7364

from openssl.

Cool, I'll wait for them to accept the pull request and use the pod once
its "live".

Thanks!

Tom

On Tue, Jan 28, 2014 at 1:18 PM, Marcin Krzyzanowski <
[email protected]> wrote:

CocoaPods/Specs#7364 CocoaPods/Specs#7364

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33469806
.

from openssl.

Merged as OpenSSL-Universal in Cocoapods public repository.

from openssl.

Looks great.

Thanks for all the effort!

Tom

On Wed, Jan 29, 2014 at 5:24 PM, Marcin Krzyzanowski <
[email protected]> wrote:

Merged as OpenSSL-Universal in Cocoapods public repository.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33593937
.

from openssl.