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

Add brew post-install troubleshooting tips #93

Open
dmarcotte opened this issue May 4, 2023 · 3 comments
Open

Add brew post-install troubleshooting tips #93

dmarcotte opened this issue May 4, 2023 · 3 comments
Labels
Developer Wanted Great issue up for grabs

Comments

@dmarcotte
Copy link
Owner

There are a couple of important and common pitfalls users run into when install/upgrading Easy Move+Resize. For folks installing manually from this github repo, the install instruction have a troubleshooting section to help out.

brew users though, especially on upgrade, will not see this section which can cause problems and confusion. We can hopefully give them a bit of help too...

I imaging it's possible to configure some post-install notes like I've seen from many other brew packages to link to the troubleshooting section section so that even brew users have a chance to spot the tips as they need them.

@dmarcotte dmarcotte added the Developer Wanted Great issue up for grabs label May 4, 2023
@dmarcotte
Copy link
Owner Author

@metakirby5, @GianniTM, @victorpopkov, @suschizu — hey y'all. @mention'ing everyone here for two reasons:

  1. most importantly, to say: THANK YOU! I only just realized that bumping the version for the cask install was a manual process, and I really appreciate all your help maintaining it. (Side note: is it an easy process? Can/should we add a note to the Release Process documentation to add this step?)

  2. is this change described in this issue easy and would any of you be able to provide tips on how to accomplish this or even just go ahead and implement? (No pressure to do anything here—like I said, the important point is 1. above 🙏 )

@metakirby5
Copy link

Hello! To be honest, I forgot I had even added the cask in the first place 😅

  1. IIRC it should be a pretty easy process, where we only need to change the version number and SHA based on the instructions, and submit a PR. I think it would be great to add more documentation, as you mentioned!
  2. I think you can use the caveats stanza.

@dmarcotte
Copy link
Owner Author

Thank you, @metakirby5!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Developer Wanted Great issue up for grabs
Projects
None yet
Development

No branches or pull requests

2 participants