-
Notifications
You must be signed in to change notification settings - Fork 49
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
Cocoapods Spec Uses the Wrong Repo For Pluralize #14
Comments
Yes, wonderful. For others coming across this you can specify the repo in your Podfile like this: pod 'Pluralize.swift',
git: '[email protected]:joshualat/Pluralize.swift.git',
branch: 'master' |
@joshualat @sammy-SC Can you push an update to cocoapods? |
@paulnicholson This repo appears to be abandoned. Best bet is to clone it and maintain yourself or simply grab the Pluralize.swift source file and drop it into your own project. |
@DavidLari Using this repo in the podfile like |
That's true, but the 'maintainer' has shown no interest in responding to any issues, thus I would consider it abandoned and plan accordingly. In my case, I just copied the relevant source file into my project and edit as needed. |
Hello @DavidLari @paulnicholson , I apologize for late response. I believe the project has been abandoned and I recommend the same thing as @DavidLari |
While the podspec on this repo references joshualat/Pluralize.swift, the one that you get by doing
pod 'Pluralize.swift'
is actually @sammy-SC's fork, which hasn't been updated for a while and is still using Swift 1.2.I'm not quite sure what the process is for fixing that at the moment, just figured I'd log it here.
The text was updated successfully, but these errors were encountered: