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

Modify macOS build files to only allow GUI launch on supported OS versions (and associated documentation change) #1260

Merged
merged 7 commits into from
Nov 4, 2021

Conversation

jgrisham
Copy link

Updated README.md and Info.plist file for macOS distribution to clarify OS version requirements (and to prevent launch crash report messages when launching Barrier on unsupported OS versions).

Merging this with the master branch should resolve issue #544.

Updated LSMinimumSystemVersion to prevent launch on unsupported macOS versions.

Release notes for 2.3.0[1] state that macOS 10.12 is the minimum - this has not been verified in the code, however.

[1] https://github.com/debauchee/barrier/releases/tag/v2.3.0
Updated OS support section, based in the discussion from issue debauchee#544.

(Also cleaned up code formatting in FAQ section)
@jgrisham jgrisham changed the title Patch 1 Modify macOS build files to only allow GUI launch on supported OS versions (and associated documentation change) Aug 24, 2021
@Unknown-Guy
Copy link

Using Barrier on Win11, works the same as on 10, haven't noticed any differences. Maybe could be considered as supported OS.

Copy link

@shymega shymega left a comment

Choose a reason for hiding this comment

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

Apart from the niggles I commented about, this looks like a great PR. Congrats! If you could add a newsfragment entry, as documented (I think) in the repo, and rebase against master, that'd be great - and we can then merge.

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@shymega
Copy link

shymega commented Nov 3, 2021

Looks like we have a merge conflict.

@jgrisham
Copy link
Author

jgrisham commented Nov 4, 2021

Looks like we have a merge conflict.

I think I fixed that with a manual re-base of my patch branch with the current project master branch.

(Having never done that manually before, there may be an extraneous commit in the history; perhaps that artifact won't import when this PR is merged.)

@shymega
Copy link

shymega commented Nov 4, 2021

This looks great! I'm happy to merge, and there's no conflicts with master, so let's go for it 💯

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

Successfully merging this pull request may close these issues.

4 participants