Add gtk+3.

[Midar]

No description provided.

[jacknagel]

On 10.6 I get this:

checking X11/extensions/XInput2.h usability... no
checking X11/extensions/XInput2.h presence... no
checking for X11/extensions/XInput2.h... no
checking for XIAllowTouchEvents... no
configure: error: *** XInput2 extension not found. Check 'config.log' for more details.

The docs (http://developer.gnome.org/gtk3/3.4/gtk-building.html) advertise "--disable-xinput", but configure does not accept it.

[jacknagel]

Here's why:

http://git.gnome.org/browse/gtk+/commit/?id=962a5d8b8a457a7829555596d872f9180ceaf829

[Midar]

Interesting, it works for me. Is your X11 outdated, maybe?

[jacknagel]

It's as up-to-date as it can be on 10.6.

[Midar]

So you are using the latest Xquartz? Interesting. I'm using the latest Xquartz on 10.7 and there it works. Wonder why they would have so different versions of Xquartz for 10.6 and 10.7?

So, just require 10.7 for this package?

[jacknagel]

I am using the stock X11 that ships with SL + whatever updates Apple officially shipped.

Currently Homebrew doesn't support using the separate XQuartz package, so formulae have to assume the stock X11.

(That will have to change for Mountain Lion, obviously, but for the time being...)

[Midar]

Requiring the X11 that comes with SL is a really bad idea - it's totally outdated and nobody who is actually using X11 is using it anyway. Apple will drop it in ML because nobody is using it.

Can we have an option to require Xquartz please? Everybody who does something serious with X11 has it installed anyway. Or should I try with stock X11 in 10.7 and require 10.7 if that works?

[jacknagel]

It's fine to use XQuartz, but we can't require it nor provide support for it because none of the maintainers have it installed/use it.

[Midar]

So what's the solution to get gtk+3 finally in? I've been trying for so long now… gtk+3 is standard in the Unix world for a long while already, it starts to get embarassing that it's not in homebrew.

[jacknagel]

If you can give it a go with the stock X11 on 10.7 and it works, we can maybe let it in as 10.7 only and sort out out the 10.6 situation later.

[Midar]

I have no way to test with the stock X11 from 10.7 as it seems Xquartz just adds the headers to /usr/X11/include and I have no idea which ones came form Xquartz. Can someone else with 10.7 please test?

[jacknagel]

Doesn't Xquartz install stuff to /opt/X11?

[jacknagel]

BTW I bumped some previous discussion about Xquartz on the mailing list: http://librelist.com/browser/homebrew/2012/2/18/clouds-on-the-horizon-for-x11

Though the latest messages haven't posted yet.

[Midar]

Oh, I assumed it puts headers in /usr/X11/include or even /usr/include/X11 in order to be found automatically. It seems I was wrong. I guess Xquartz wasn't used for compilation then. To verify, I'm going to rename /opt/X11 and try building it again.

[Midar]

Build worked fine. What would be the correct way to require Lion? I couldn't find any other forumla requiring Lion.

[adamv]

I am against adding GTK+3 as Lion only if we can at all support it on Snow Leopard; it will cause a cascade of SL-unsupported stuff

[Midar]

If only gtk+3 has the dependency on Lion and not stuff depending on gtk+3, it can be easily ported to SL later. If someone wants to use it on SL, that person would just have to add Xquartz support to Homebrew and change gtk+3 to use Xquartz if not on Lion and all stuff depending on gtk+3 will just work. So where exactly is the problem? As said, it's quite embarrassing that gtk+3 still isn't in Homebrew, considering how everybody in the Linux world already switched to it and considering how many programs require it, so I really think delaying it any further is a really bad idea.

[jacknagel]

Merged.

[ghost]

@jacknagel Is it now okay to update the GTK+ packages to versions that require GTK+ 3.x, or should we stick with 2.x compatibility for the time being?

[jacknagel]

Hmm. I guess it depends on what users expect. Perhaps someone could create a tap with gtk+3 versions of the packages for the time being?