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
Ruby (MRI) scraper #3
Comments
I saw rbenv/ruby-build#882 patch. Did you scrape from https://rubinius-releases-rubinius-com.s3.amazonaws.com/index.txt ? If it's true, I will prepare digest hash list of CRuby compatible rubinius format. |
yep! the rubinius scraper is in #2 (https://github.com/jasonkarns/ruby-build-update-defs/pull/2/files#diff-83ea838d1f1ef90b299cc1478d161c33) But honestly, I think an easier format might be a simple TSV
or perhaps:
The second format would allow easily publishing multiple checksums in various formats (md5, sha2-256, sha2-512, etc) for each release. Basically, I've set up this plugin to support multiple scrapers, assuming that each ruby would require it's own scraper. There's no need to base it off of rubinius' format, but rather, do what's best for your project and build process. Copying rubinius' format might make this scraper trivial in the short term, but I don't think their format is the most robust. So it's entirely up to you! Feel free to post notes here as you have drafts of the release manifest (for lack of a better term), and I'll take a stab at the scraper for it, providing any feedback from there. |
@hsbt any progress on cruby manifest file (for scraping?) |
No progress :( Please wait several weeks... |
@hsbt awesome! Might I suggest just a couple tweaks?
Using 2.3.0 as an example:
Many thanks for publishing the manifest file. These tweaks would make parsing a bit easier, at least for POSIX shell tooling. Edit: Apologies. I just noticed that there are multiple files published per version so I've update my comment above |
I applied your suggestions. Please confirm http://cache.ruby-lang.org/pub/ruby/index.txt |
@hsbt Great! I've finished and merged the scraper in #9. Running the scraper also found a bunch of old rubies that didn't exist in ruby-build. I've opened rbenv/ruby-build#949 for them. Ideally, this now allows the ruby-build definition process to be fully scripted, as I've done with node-build. I intend to open a PR to ruby-build soon with a script for the full process. Thanks! |
No description provided.
The text was updated successfully, but these errors were encountered: