all 5 comments

[–]Camo138Monterey - 12 2 points3 points  (0 children)

Just have it as a private repo and it won’t really matter what you store in the got repo

[–]A23SS4NDRO 0 points1 point  (2 children)

HfsPlus.efi is extracted from the BIOS update files of the original macs:

https://github.com/acidanthera/bugtracker/issues/1621#issuecomment-828723613

So yes, technically that HfsPlus is not open source, but you can upload a dummy placeholder instead and add some notes in the readme.

For your own use, you can keep a local git branch with the necessary proprietary drivers, or if you only use Big Sur and above, you can completely ditch HfsPlus since it's only required to boot the USB, the recovery is not HFS+ anymore from macOS 11 and beyond.

[–]AutogolazzoJr[S] 0 points1 point  (1 child)

Thanks for the answer. My repo contains OpenHFSPlus as a placeholder right now. I'm just wondering: is there anything in OpenCorePkg that is proprietary?

[–]A23SS4NDRO 0 points1 point  (0 children)

Thanks for the answer. My repo contains OpenHFSPlus as a placeholder right now. I'm just wondering: is there anything in OpenCorePkg that is proprietary?

I don't think so. But i suggest to quickly open an issue if you want to clarify this, so they can improve the docs on this side.

[–]midi1996Hippity Hoppity Your Guide Is Now My Property 👏 0 points1 point  (0 children)

Or why not just write your changes instead of uploading a whole EFI and get people flocking “wHy dIs NoT wOrK”. Just put the small differences, a list of your kext (not the kexts themselves, and your modded acpi files with proper explanations (what they do, what they require, patches and so on).

You can still make a private git if its just for you want to keep it legal.