-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
[WIP] brew cask outdated #9490
[WIP] brew cask outdated #9490
Conversation
Prerequisite for new |
This is exciting! What else needs to happen here before this PR is merged? I looked through issue #9403 but don't see any further requisites since it looks like support for |
Update Google Adwords Editor to 11.0.3
Revert "Update Google Adwords Editor to 11.0.3"
✅ Please merge this. It's super useful. |
Any word on why this is stalled? Using |
@phinze is this still WIP? |
What are we waiting for? Add a test case before merge this? |
let's merge this 👍 |
@salimane No, lets not merge this. It is clearly marked as a work in progress. Why would we just merge it? |
@victorpopkov my bad, I was just excited to see this being worked on :) |
Anyone else is welcome to pick up this work, but I'm not pushing it forward anytime soon. Closing to reduce repo noise. |
Guys, for those who have been waiting for years the unicorn-ish See: https://github.com/bgandon/brew-cask-outdated Any help for packaging a Homebrew formula would be more than welcome! Cheers |
@bgandon 👍 |
@salimane Again, I ask you refrain from useless “+1” and thumbs up comments. They only add noise. @bgandon It’s always the users who never contributed and know nothing of the project that act the more entitled. I saw your deleted comments, and your absolute disrespect for the team paints you as the type of person that causes open source maintainers to burn out. If all you wanted was a script, other users have done them in the past and presented them here respectfully and amicably. You’re not special, and your script isn’t impressive. Why not you make the contribution to the core itself? Once the new install behaviour is implemented (which is only getting sooner), your script will stop working, because the method you use to check for outdated versions is deeply unreliable now and will completely break under the new behaviour. No, this is not a simple addition like you valiantly claimed it is, and you would’ve known that if you read the issue linked in the huge bold letters at the top of the README. We’re not here to serve you. We define priorities by what we feel is important and what the team has time to work on. Many small things need fixing before we can tackle big things and do them well. If you felt some things needed to exist already and didn’t understand why they didn’t, you should’ve asked and we would’ve told you. I kindly ask you take your toxic atitude elsewhere. You’re no longer welcome. Locking the issue since nothing of worth was added since it was closed. Anyone that wants to pick up the effort already made here is very welcome to do so. |
My appologies to the other intervenients in this issue, but I take the responsibility of managing this project seriously, and find it abolutely disrespectful when someone appears from nowhere with no history of contributions or meaningful interactions and starts making demands of the free time of others and insulting the team of maintainers (even if those comments were since deleted). |
No description provided.