[MacPorts] #44414: cairo +quartz pango +quartz

[MacPorts]

#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 sean@…):

 Replying to [comment:6 ryandesign@…]:
 > Many ports that don't actually have any x11 or quartz code nevertheless
 build themselves differently depending on whether the x11 or quartz
 variants of their dependencies are selected. That's why those ports also
 have needed to have x11 or quartz variants. That need would go away for
 gconf if all of the ports gconf depends on no longer need their x11 and
 quartz variants. I don't know if that will be the case.
 >
 > My hesitation in making this change is ports like py-cairo which contain
 code like this:
 >
 > {{{
 >     variant x11 {
 >         require_active_variants path:lib/pkgconfig/cairo.pc:cairo x11
 quartz
 >     }
 >
 >     if {![catch {set result [active_variants
 path:lib/pkgconfig/cairo.pc:cairo x11 quartz]}]} {
 >         if {$result} {
 >             default_variants +x11
 >         }
 >     } else {
 >         default_variants +x11
 >     }
 > }}}
 >
 > This seems wholly wrong, even now, and will be wronger once pango and
 cairo are changed to no longer have x11 and quartz variants. Sean, how
 shall we handle this? Do we just remove that code once pango and cairo are
 changed?

 I must admit that this code block is from my early days in macports. It
 was copy-n-pasted most likely. It's fine to remove, I think.

-- 
Ticket URL: <https://trac.macports.org/ticket/44414#comment:7>
MacPorts <https://www.macports.org/>
Ports system for OS X