Changing "grafx2" package from a "cask" to a "formula". #6605
Replies: 2 comments
-
|
We can migrate the cask to a formula. That would require writing a formula, and then removing the cask. Users will be informed about the migration. We do not want formulae that build |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the fast response! I will check the documentation on creating a "formula" and try to test it with a local tap on my Intel and Apple Silicon Macs. If I cannot create .app, which is understandable, am I allowed to create an AppleScript file that executes the binary, that maybe the formula copies to the "/Application/" directory automatically, or alternatively that users could manually copy there from the "/opt/homebrew/share/grafx2/" directory? Best wishes, John |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew configOutput of
brew doctorDescription of issue
As mentioned in a recent comment by GrafX2's lead developer Adrien Destuges to this closed Homebrew issue ...
Homebrew/homebrew-cask#205688
The GrafX2 development team do not make official binary Mac builds of GrafX2 because none of them own a Mac, and the few ancient GrafX2 Mac builds that are available for download on their site are out-of-date, unsupported, and often broken on current Macs.
I have been working with them to bring their project's Mac compilation up-to-date and functional with Homebrew on current Apple Silicon Macs, and I am able to build a functioning executable with what is currently checked-in to their official gitlab repository here ... https://gitlab.com/GrafX2/grafX2
Two questions ...
How can we go about changing Homebrew's official GrafX2 package from being a "cask" that points to one of these ancient and unsupported Mac builds into a "formula" that builds GrafX2 from the official and supported repository source code?
When we do build GrafX2 as a "formula", would it be better to leave it as an SDL2 GUI executable in "/opt/homebrew/bin" that uses Homebrew's SDL2 libraries in the "/opt/homebrew/lib" directory tree as is currently working, or would it be OK to have the formula build either an unsigned or a locally-signed Application package to go into the "/Applications/" directory?
Best wishes,
John
Beta Was this translation helpful? Give feedback.
All reactions