[MacPorts] #58234: kitty: Also offer the X11 version (was: Kitty is using native libraries)

[MacPorts]

#58234: kitty: Also offer the X11 version
--------------------------+--------------------
  Reporter:  EvanCarroll  |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  kitty        |
--------------------------+--------------------
Changes (by ryandesign):

 * type:  defect => enhancement


Comment:

 The situation described in the FAQ is different from the one you are
 experiencing with Kitty.

 The FAQ entry describes this situation: a port links with, say,
 /usr/lib/libz.1.dylib. This is undesirable: we want it to link with
 /opt/local/lib/libz.1.dylib instead, because the MacPorts copy of zlib is
 newer than the macOS copy and is updated more frequently.

 The situation with Kitty is that Kitty, or at least the part of it that we
 build in the kitty port, is a macOS Cocoa application, but you would like
 it to be an X11 program. It looks like Kitty is cross-platform and does
 use X11 on non-Mac operating systems, so it seems plausible that the X11
 version could also be compiled on macOS. If so, we could potentially offer
 the X11 version of kitty alongside the macOS Cocoa version, perhaps by
 defining an +x11 variant in the kitty port, or by offering a separate
 kitty-x11 (sub)port. I don't believe anybody has attempted to do that yet.

-- 
Ticket URL: <https://trac.macports.org/ticket/58234#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS