-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Drop the iso_checksum_type & iso_checksum_url fields #8437
Changes from 30 commits
a22608f
2d3c045
1b993b8
aedd549
fc60b59
7bc47b8
f6d39fc
596b315
6617f13
5967c76
61f751d
271dde1
0ba1597
8d3978b
c3160e6
d44d7e2
afe93ac
b293a09
39444b3
4535dec
9615b3b
39b50a5
421ca5d
558c0fa
799bedf
23fd311
9101ae0
bdb8b09
3e60725
8d1aabb
24758a1
43ece44
517718c
0513d38
49c2baa
594edd5
7c183d1
1daf880
368bcc1
8bb8470
0a4d4e5
dd02f07
6f97b5b
0264368
ae6dd4f
443456b
cadbcca
23c96d3
486a967
6bf844f
cf25108
a802561
41aadc5
90e6f08
94399e9
eef3d7d
98af124
da5f794
fc8b708
8e432c9
3910f62
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path
can be a URL and a file path, but does it work likefile:http://foo.com/bar
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think giving an actual example with a real checksum hash will be helpful here so users don't get hung up on the variable syntax.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added examples but for a checksum the go getter will first try to split the url with the first found semicolon and then what's left will be used to be fetched.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, weirdly enough a url can be:
file:file://./path/to/file.sum