Skip to content
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

update test suite to use sha256 #3541

Merged
merged 1 commit into from Mar 15, 2014

Conversation

rolandwalker
Copy link
Contributor

also convert no_checksum to sha256 :no_check in some cases

also convert no_checksum to sha256 :no_check in some cases
@alebcay
Copy link
Member

alebcay commented Mar 14, 2014

It seems no_checksum is being phased out at this point, at least in these examples. Should CONTRIBUTING.mdand other docs reflect that at this point, or should we wait a bit longer?

@rolandwalker
Copy link
Contributor Author

Best to wait on Casks and instructions for Casks. Not everyone has updated code which would support the new syntax.

Within the test suite, the same constraint does not apply: if someone is running the tests, they have the code.

rolandwalker added a commit that referenced this pull request Mar 15, 2014
@rolandwalker rolandwalker merged commit c6ea492 into Homebrew:master Mar 15, 2014
@rolandwalker rolandwalker deleted the testsuite_checksums branch March 15, 2014 01:11
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants