-
Notifications
You must be signed in to change notification settings - Fork 33
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
Machine-readable version of "Last available"? #5
Comments
Yeah it's quite a nice idea, and I'd say we can actually have both a single json that contains all the info and a set of files with dates. |
So what I came up with so far is generating a file tree like the following So the data will be fetchable via a link like |
That sounds pretty awesome! So I can just do |
Yep! No json with all the info gathered in one place yet, but I hope I'll
come up with a viable solution in the next few days for that matter as well
…On Sun, Jun 9, 2019, 12:05 AM Ralf Jung ***@***.***> wrote:
That sounds pretty awesome! So I can just do nightly-$(curl
http://rust-lang.github.io/rustup-components-history/last-available/x86_64-unknown-linux-gnu/miri
) to figure out the last nightly with miri?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AA3RGDJCKSRJHC7SWIM5KTTPZQNKNA5CNFSM4HS3JMU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXH6IXY#issuecomment-500163679>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA3RGDN3VSZZZF3VQKXXZV3PZQNKNANCNFSM4HS3JMUQ>
.
|
Well this is already enough for my usecase, but there are probably others. :) |
🎉 |
I think I'll put on ice making a combined json file and close the issue for now :) |
Awesome, thank you so much. :) I'll play around with this later. |
For use-cases like running nightly Clippy or Miri on CI, it would be very useful to be able to determine the last version of rustc that had that component included. This site has all the necessary information for that, but it is not available in a machine-readable way. Do you think that would be a reasonable extension?
I could imagine either a JSON file (so a script could use
jq
), or maybe just one file per component containing the latest date (so plaincurl
is enough --jq
IIRC is not available on macOS with Travis).The text was updated successfully, but these errors were encountered: