-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update podspec to remove dependencies #3
Comments
Hmmm. I don't use this project nor Cocoapods, but will merge a PR that solves this. |
This is an even bigger issue now! :) The dependencies don't specify a version, so it automatically pulls down the latest, which is a build-breaking 2.0.0-beta. That unfortunately overrides the version that I want to be pulled down ( Have you identified yourself as the owner of the pod yet? I'm unsure if it's still possible for random people like me to update the Specs repo. |
I've claimed the pod. Send a PR with the changes and I'll update it. |
Sorry, I need more details. PR to where? The main Specs repo, or here by adding the podspec? |
Here, the main repo. |
I think the cocoapods works fine as this podspec file. Are you sure that it be cause by the cocopods? |
I'm not sure I understand what happened to this repo? We're seeing issues since yesterday as well. This is due to the pods not specced to a specific version and CocoaLumberjack is updating to their beta version. The commit for version 1.2 of this repository is missing in this repository but is being referenced by Cocoapods. |
Ugh, I'm not really using this at all (neither do I use cocoapods). What should I do to fix it? |
@maarek You can override the version that's pulled via dependency by specifying the version of CocoaLumberjack you want first, followed by this pod. |
I think, it is not support CocoaLumberjack 2.0.0-beta4, and it is another issue. But, this issue is talk whether the dependency to CocoaLumberjack should add the pod spec. |
Unfortunately, it's hard to use this as a pod when I want to exclude NSLogger and the connector for
Release
builds.Because CocoaLumberjack is listed as a dependency, it is linked twice in this instance, causing a duplicate symbols error. I think it's safe to assume that if you are using the connector, you'll know what base tools are needed.
I've opened this issue here since the Specs repo is more locked down now.
The text was updated successfully, but these errors were encountered: