Homebrew was created to add the package manager experience of Linux to Mac OS X, so what gap does this fill?
Mac users already experience issues relating to having multiple non-default package managers (i.e. Homebrew and MacPorts) - what conflicts will having a default and non-default package manager arise?
The problem it is trying to solve would be better approached hosting Debian, RHEL etc repositories which mirror each other in their structure.
Mac users already experience issues relating to having multiple non-default package managers (i.e. Homebrew and MacPorts) - what conflicts will having a default and non-default package manager arise?
The problem it is trying to solve would be better approached hosting Debian, RHEL etc repositories which mirror each other in their structure.