Linuxbrew – A fork of Homebrew for Linux • Hacker News Board

Conflicting with the system's package manager is obviously the most problematic issue with porting homebrew to linux, and I can imagine there's many more caveats that would render such a thing pretty useless.

Re: Linuxbrew – A fork of Homebrew for Linux

#5

Post by zz1 » Thu, Apr 09, 2015, 3:55 PM UTC

Honest question.

Homebrew is the missing package manager for OS X. Linux has package managers, so why a fork? Packages just available through homebrew?

Re: Linuxbrew – A fork of Homebrew for Linux

#6

Post by ics » Thu, Apr 09, 2015, 3:56 PM UTC

drivingmenuts wrote: post #3

I'm actually surprised this wasn't done sooner.

It's been in the works for a while (>1 year) but maybe now it's stable. Good for them!

Re: Linuxbrew – A fork of Homebrew for Linux

#7

Post by untitaker_ » Thu, Apr 09, 2015, 3:59 PM UTC

zz1 wrote: post #5

Honest question. Homebrew is the missing package manager for OS X. Linux has package managers, so why a fork? Packages just available through homebrew?

I personally have always hoped for a unified package manager across distros.

Re: Linuxbrew – A fork of Homebrew for Linux

#8

Post by totalrobe » Thu, Apr 09, 2015, 4:02 PM UTC

drivingmenuts wrote: post #3

I'm actually surprised this wasn't done sooner.

why?

Re: Linuxbrew – A fork of Homebrew for Linux

#9

Post by jamescun » Thu, Apr 09, 2015, 4:03 PM UTC

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.

Re: Linuxbrew – A fork of Homebrew for Linux

#10

Post by adamwong246 » Thu, Apr 09, 2015, 4:06 PM UTC

but why?