mirror of
https://github.com/Installomator/Installomator.git
synced 2026-03-08 03:22:12 +00:00
Feature Request: Leverage Homebrew Catalog #39
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maumeerally on GitHub.
All questions must be filled out or your Issue will be closed for lack of information
What's the bug?
This is a feature request, if I have filed this in the wrong place then please educate me on the correct place and accept my apologies in advance.
Have you confirmed this Issue has not been reported already? (Check open Issues and Pull requests)
I did search for it, but could not find a similar request.
Installomator version
Installomator V10.8 - March 28th 2025.
Additional context
It would be great if Installomator could have an option to leverage the Homebrew JSON catalogue here https://formulae.brew.sh/api/formula.json
We provide the homebrew label and then Installomator leverages https://formulae.brew.sh/api/formula.json to obtain the download URL. There are over 5,000 software title labels actively maintained here. Far more than all the labels in Installomator.
Installomator log
Not Applicable
@wakco commented on GitHub:
First, not a bug, second, Installomator has a label for installing homebrew, and third, homebrew has to compile those projects, while Installomator handles installing apps that are already compiled, and usually packaged, in short Installomator is not wrong tool for the kinds of things homebrew installs.
Best advice we can give you, use Installomator to install homebrew, then use homebrew to install what you are wanting from homebrew. If installing homebrew is not an option, then consider other similar tools, such as macports.org
@maumeerally commented on GitHub:
Thank you for your feedback. I do have to make one correction to your observation. You do not need to compile anything. If you take a look at the JSON catalogue first: https://formulae.brew.sh/formula/
I will give you one example: https://formulae.brew.sh/api/cask/google-chrome.json
The JSON, like every other cask title, has "url" which contains a download link which is regularly updated by this GitHub automation: https://github.com/Homebrew/homebrew-cask/actions/workflows/autobump.yml
However I will take your feedback onboard and discontinue the use of Installomator and just use homebrew instead.
Thank you.
@wakco commented on GitHub:
As a Mac administrator, I have to say that sadly Chrome is a bad example, homebrew downloads the dmg, Installomator has a label for the dmg, however Installomator also has a label for grabbing the admin friendly pkg (package) install. Also Installomator uses a more secure code signing check of what was downloaded against the Apple Developer "Team ID", which the homebrew formula's do not contain, instead of the checksum that homebrew is using (at least in Chromes formula), however the Team ID is a vital part of how Installomator works.
As for what I stated previously, Chrome is only an example of what homebrew is capable of, not an example of a typical homebrew install that usually requires compiling at install time.
@maumeerally commented on GitHub:
Yes, but homebrew does support installing a pkg and is an open source project (I can link you to casks that have a pkg for the download url). And for example, if we have a preference for a Chrome pkg we can we can submit that as a separate title.
And whilst you are right about the Team ID checks, you do not acknowledge Installomator's biggest weakness in me raising this feature request; that it relies on a static list for checks for download links that is updated once every couple of months.
@wakco commented on GitHub:
Then ask for that, an automated process to help update the dated labels. What was asked for was to essentially dump the chosen way of working for another tools way of working, which in the end was really asking for Installomator to be something it wasn't, all while there is already something working that way (homebrew).
That said some things;
@wakco commented on GitHub:
And since I just realised it, another reason Chrome was a bad example, homebrew is also using a fixed download URL, just like Installomator, but unlike Installomator requires that automation to update the checksums and version information, both things Installomator generally doesn't require updating in the label because the version is looked for from the developer and not stored in the label, while a Developer's Apple Team ID only changes for an app when the app changes developers, which for Installomator really means it is a new app.
@maumeerally commented on GitHub:
I think you need to actually read my post when replying to it:
What I said: