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

Delete binreader cask #6690

Merged
merged 1 commit into from
Oct 15, 2014
Merged

Delete binreader cask #6690

merged 1 commit into from
Oct 15, 2014

Conversation

lukateras
Copy link

Their site doesn't seem to be functioning:

Nor I found any other reliable place to download it.

Their site doesn't seem to be functioning http://www.binreader.com/
vitorgalvao added a commit that referenced this pull request Oct 15, 2014
@vitorgalvao vitorgalvao merged commit 3cca216 into Homebrew:master Oct 15, 2014
@rolandwalker
Copy link
Contributor

I agree about these deletions, and am grateful to @yegortimoschenko for the tremendous contributions.

But sometimes a site goes down only temporarily. For example, manytricks.com was down just today, so their associated Casks didn't make it into #6686. But now I see that manytricks.com is back up.

So, I propose to create a homebrew-boneyard repo within the caskroom org, by analogy with Homebrew's boneyard:

  • seemingly dead Casks could be placed in the boneyard for other contributors to find
  • "documented dead" Casks like bodega.rb would just be deleted, no need to use the boneyard
  • knowing the backstop is present would encourage us to delete more freely
  • at our current size, deleting must become a necessary habit of maintenance. Feeling free to delete would be a good thing.

@lukateras
Copy link
Author

@rolandwalker That would be great.

@lukateras lukateras deleted the delete-binreader branch October 16, 2014 06:35
@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