#44414: cairo +quartz pango +quartz --------------------------+-------------------------- Reporter: vtjnash@… | Owner: ryandesign@… Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: cairo pango | --------------------------+-------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => ryandesign@… * port: => cairo pango Old description:

Since cairo and pango seem perfectly able to install themselves with both cairo and pango support enabled, it seems unnecessary (and in some cases detrimental) to artificially limit the capabilities of the installed code. Instead it seems a better default for these libraries would be:

+quartz +x11

Or to just eliminate these two options altogether.

As mentioned in previous tickets (e.g. https://trac.macports.org/ticket/31148#comment:3), in the distant past this was not possible. however, now the existence of these options just seem like an unnecessary annoyance to the user. It feels like this is just a historical artifact: is there a more recent reason that this must still be the case?

(Similarly, the restriction preventing building gtk3 +x11 +quartz seems to be artificial, since the backend can be selected at runtime via environment variable: GDK_BACKEND=quartz https://developer.gnome.org/gtk3/stable/gtk-running.html)

New description: Since cairo and pango seem perfectly able to install themselves with both cairo and pango support enabled, it seems unnecessary (and in some cases detrimental) to artificially limit the capabilities of the installed code. Instead it seems a better default for these libraries would be: +quartz +x11 Or to just eliminate these two options altogether. As mentioned in previous tickets (e.g. comment:ticket:31148:3), in the distant past this was not possible. however, now the existence of these options just seem like an unnecessary annoyance to the user. It feels like this is just a historical artifact: is there a more recent reason that this must still be the case? (Similarly, the restriction preventing building gtk3 +x11 +quartz seems to be artificial, since the backend can be selected at runtime via environment variable: GDK_BACKEND=quartz https://developer.gnome.org/gtk3/stable/gtk-running.html) -- -- Ticket URL: <https://trac.macports.org/ticket/44414#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#44414: cairo +quartz pango +quartz --------------------------+-------------------------- Reporter: vtjnash@… | Owner: ryandesign@… Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: cairo pango | --------------------------+-------------------------- Comment (by larryv@…): Replying to [comment:3 ryandesign@…]:

I would like to do this—remove x11 and quartz variants from pango and cairo and make both backends on all the time

OMG YES PLEASE FOR THE LOVE OF GOD -- Ticket URL: <https://trac.macports.org/ticket/44414#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X