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.

Sign up for GitHub

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

Jump to bottom

Improve version reuse in GDAL Framework #7153

Closed
wants to merge 1 commit into from
Closed

Improve version reuse in GDAL Framework #7153

wants to merge 1 commit into from

Conversation

tapeinosyne
Copy link
Contributor

Closes #6330.

This cask will still break when the package found at the URL is updated again. An alternative would be to use :latest, which would only break if the URL itself changes.

@alebcay
Copy link
Member

alebcay commented Nov 7, 2014

So do you think we should merge in this temporary fix or just change it to :latest for good?

@tapeinosyne
Copy link
Contributor Author

:latest would break less often. This is generally true for all vendors updating packages in-place for minor releases.

@tapeinosyne tapeinosyne mentioned this pull request Nov 10, 2014
Closed
@rolandwalker
Copy link
Contributor

Fixed merge conflict caused by me, and merged as 7bd03e9.

@tapeinosyne tapeinosyne deleted the gdal branch February 18, 2015 16:45
@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.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

SHA2 mismatch on gdal-framework install
3 participants
@tapeinosyne @alebcay @rolandwalker