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 39 casks to use versioned urls (Batch 1, A-K) #13115

Merged
merged 39 commits into from
Aug 9, 2015

Conversation

scribblemaniac
Copy link
Contributor

No description provided.


url 'https://macrabbit.com/espresso/get/'
appcast 'https://update.macrabbit.com/espresso/2.2.3.xml',
url "https://s3.amazonaws.com/macrabbit/downloads/Espresso%20#{version}.zip"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment # amazonaws.com is the official download host per the vendor homepage is missing. Even if there is a redirect from official URL https://macrabbit.com/espresso/get/.

@vitorgalvao
Copy link
Member

@scribblemaniac Where are you finding all these, even? Many of them are quite hard to find, and I sincerely worry these changes actually make them harder to upgrade.

@scribblemaniac
Copy link
Contributor Author

@vitorgalvao The weren't all that difficult for me to find. They are all found either on a homepage or in an appcast feed. Certainly latest casks are easier to upgrade, but I wasn't the one who decided that this was a good idea. Perhaps you need a refresher on why this decision was made: #1021.

@vitorgalvao
Copy link
Member

No need, I remember the discussion well. I was against it for a long time, until being convinced. Funnily enough, plans for upgrade changed and things like casks that can auto-update will be excluded from that process, so the only argument justifying this now is security.

In the previous comment I didn’t mean “upgrade” as in “upgrading installed apps”, but as in “updating the cask files themselves”, i.e. if these links were hard to find, other collaborators wouldn’t find them and casks would remain frozen in an older version. If those were easy to find after all, no big deal.

@scribblemaniac
Copy link
Contributor Author

Maintainers shouldn't have to worry about finding the links though, all they should need to do is modify the version string. If the new version doesn't work with these links, they can simply use whatever link is on the homepage and assume that this link format is not being supported anymore.

@vitorgalvao
Copy link
Member

Agreed.

@scribblemaniac scribblemaniac force-pushed the switch-versioning-1 branch 2 times, most recently from 6373483 to 244010d Compare August 9, 2015 22:29
@scribblemaniac
Copy link
Contributor Author

Okay, I'm pretty sure I've fixed everything brought up so far and then some. Thank you @vitorgalvao and @victorpopkov for having patience with me. I don't know why I keep making stupid mistakes like these, hopefully the next time will go smoother.

@victorpopkov
Copy link
Member

Everything looks good. Thank you for all the patience in making all the changes and for the contribution of course.

victorpopkov pushed a commit that referenced this pull request Aug 9, 2015
Update 39 casks to use versioned urls (Batch 1, A-K)
@victorpopkov victorpopkov merged commit 8a192e5 into Homebrew:master Aug 9, 2015
@scribblemaniac scribblemaniac deleted the switch-versioning-1 branch November 15, 2016 06:46
@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.

3 participants