Opened 14 years ago
Last modified 3 years ago
#27990 assigned enhancement
Split GTK2 support to gtk2-x11 and gtk2-quartz
| Reported by: | bgrupe27 | Owned by: | mascguy (Christopher Nielsen) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), nonstop.server@…, mmpestorich (Mike M Pestorich) | |
| Port: | gtk2 |
Description
Hi,
since there are many problems with gtk2 +quartz (e.g. #19705 #27923 and some unreported ones) I'd like to propose to split the port (and some of its dependencies like pango and cairo) into a gtk2-x11 and a gtk2-quartz port.
Ports depending explicitly on an X11 gtk/gdk could then just require it and you could have installed both versions. When choosing "+quartz" on a port like gimp where it works, gtk2-quartz should be selected automatically.
Change History (6)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
comment:2 Changed 14 years ago by bgrupe27
This auto-detection is exactly my problem, since you have no way of knowing beforehand if this port will work with +quartz or not.
Please consider the situation of a clean macports install and just typing in "port install gnome +quartz+no_x11". It will compile many things successfully before failing at configuring bug-buddy.
Now there's no other way than to uninstall the whole GTK2 stack and reinstall it without quartz support if you want a working gnome port.
Some ports even have have broken configure scripts (like the linked libcanberra bug) and just fail seemingly randomly at compiling.
comment:3 Changed 13 years ago by jmroot (Joshua Root)
This should be easier now that we have subports. Anything in the stack that can be built in quartz or x11 flavours and has dependents needs to be two separate (sub-)ports. Anything that builds differently but has no dependents needs a variant (or two) that changes the dependencies to the appropriate quartz or x11 versions.
comment:6 Changed 3 years ago by mascguy (Christopher Nielsen)
| Owner: | changed from macports-tickets@… to mascguy |
|---|---|
| Status: | new → assigned |
I'm not sure this is a good idea.
I think there are many ports that work with gtk2 quartz that don't have quartz variants; they just use quartz if gtk2 happens to be built with quartz. This proposal would break that.
It would also require quite a bit of work, probably, to configure the new gtk2-x11 and gtk2-quartz ports so that they do not conflict with one another, and then additional work in each port that wants to use them to tell them where they're located.