-
Notifications
You must be signed in to change notification settings - Fork 950
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
CocoaPod and Framework product in repo are outdated #49
Comments
I saw that in ee6061d @gali8 updated the README Podfile snippet to point to version 2.2 with the comment "2.3 is not yet available, I'm sorry." I don't mean to be rude, but since 2.3 has been marked as a release tag on Github, why can't you just push it to the Cocoapods master repo so users can start pulling it from Cocoapods to use in the projects? |
Can we get a status update on this? |
Yes please update to CocoaPods |
+1 |
In lieu of the maintainer of this repo responding, I'd suggest someone forking the repo and making their own submission to cocoapods. I'd be willing to keep cocoapods up-to-date, however I don't have the resources currently to keep the core tesseract-ocr library up to date. Perhaps someone would like to collaborate on this? @kevincon? Ideally more than one person would be marked as contributor on the new fork so that if one person becomes unavailable the entire project doesn't come to a complete standstill. |
@zachberger I was also thinking about a solution like this. @gali8 has done a lot of fantastic work with this library, but the slow/never responses to issues and lack of active work and CocoaPods updates are unacceptable for the sole contributor of an open-source project that is used by so many people like this one. Personally I'd prefer it if we didn't fork the repo just for the purpose of updating the CocoaPod, so I have a proposal in two parts:
Then I'll create the new podspec in this repo and push it to CocoaPods so we can start enjoying up-to-date CocoaPods releases. I agree that if @gali8 does not respond then we have no other choice but to fork the library and work to make it the new central repository for this project. I'd be happy to take ownership of the fork and maintain it as well as make @zachberger a contributor (along with anyone else who actively contributes to the project). What do you guys think about that plan? |
Just a quick message as I'm heading out:
|
To put a timetable on this, I propose we move forward with a separate fork if @gali8 does not respond by December 15. |
@kevincon can you fork this repository and take leadership on it?? |
Dear guys, i like your work. How you can suppose, this is not the only project when I'm working. |
Done. Enjoy! |
The latest versions have now been tagged by @gali8 and pushed to the CocoaPods repo. The corresponding commits in this repo are: |
Thank you @gali8! |
The only different between 3.1 and 3.03 is in the readme file. You are welcome! |
Thanks you guys! |
The README says to use this line in a Podfile:
pod 'TesseractOCRiOS', '~> 2.3'
But the CocoaPods master repo does not have version 2.3 (latest is 2.22): http://cocoapods.org/?q=tesseract
I got around this by using this line in my Podfile:
pod 'TesseractOCRiOS', :git => 'https://github.com/gali8/Tesseract-OCR-iOS.git'
But the current Products/TesseractOCR.framework file in the repo is an older version that does not include the getConfidenceByX properties on the Tesseract class, so I am unable to use those.
Can someone please update the framework file stored in the repo to reflect the changes in version 2.3? Additionally, can someone submit version 2.3 to CocoaPods?
Thanks!
The text was updated successfully, but these errors were encountered: