-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
cask: skip sha256 generation on directories #13354
Conversation
Review period will end on 2022-06-01 at 14:04:32 UTC. |
7351a4d
to
cad53aa
Compare
Review period skipped due to |
Another thing I overlooked. 😰 Yeah, there doesn't seem to be a default way to get a checksum for a directory. You could always tarball it but that's probably more trouble than it's worth. I think this is a good band-aid for now but ideally we'd want to check if it's |
Might want to make sure whatever solution is adopted here can be used for #13232 too. |
Would it be possible to check for Edit: Yes, that is possible but wouldn't work with the new git sparse checkout download strategy mentioned above. |
Closing in favour of #13358 - as it avoids fetching any downloads before making a decision on shasum generation. |
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?This is an idea for fixing - Homebrew/homebrew-cask-fonts#5855
Because
svn
is used to download the fonts, theDigest::SHA256
is failing on the contents because it is a directory not a file.I have added a check to not return a value in these cases so that no shasum is stored.
The downside of running the check there is that I believe that we may still be fetching the download when the cask is
version :latest
.We could potentially add a check for URLs using
:svn
instead, however there may be other edge cases?I am not aware of a way to gather a shasum for a directory, if there is then that could be another approach.
CC: @apainintheneck