Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Support for Homebrew in Proget
-
Would be great if you supported https://brew.sh/ in Proget.
-
@yogurtearl_0881 this is the first I've heard of Homebrew... at first glance, it looks like a kind of open-source/hobbyist/alternative package manager for MacOS?
-
+1 for Brew support. Would be a great fit with ProGet to cover MacOS endpoint.
https://brew.sh/
-
Homebrew is a Chocolatey-like (open source and not first-class) package manager for macOS. It is the most commonly used way to install and manage tools and apps on macOS from the CLI.
I was actually surprised to find that ProGet doesn't support it, seeing that it has support for Chocolatey, APT, and Yum. It would definitely be a must-have for macOS support. There really isn't any other popular package manager for macOS.
Homebrew uses Git behind the scenes for fetching packages, and they do have support for adding additional feeds (called "taps").
-
Hi @jchitel_9895 ,
Thanks for the additional info! We "moved" your new topic back to this one, since we link these on this page in the docs and want to keep everything in one place: https://docs.inedo.com/docs/proget-feeds-other-types
Keep in mind that feed types are a significant initial and ongoing investment (it's a product in a product), and at first glance, Homebrew doesn't seem to make any commercial sense.
First and foremost, there doesn't seem to be a market here. Homebrew itself isn't commercialized. They tried a Kickstarted from 2013, but it seems to remain a hobby-type project. Compare that to Chocolatey (which may be a little older, and also did a kickstarter I think) -- they now have a decent size fulltime staff now.
But secondly (and on a technical level), there isn't a "Homebrew Repository" or "Homebrew Server" - as you mentioned, it's Git-based - which means all it's doing is cloning Git repositories, and probably using tags and specific repo layouts to determine packages.
Cheers,
Alex