[MacPorts] #52281: Port for evolution, based on devans at macports.org evolution-data-server
MacPorts
noreply at macports.org
Mon Oct 17 06:41:30 CEST 2016
#52281: Port for evolution, based on devans at macports.org evolution-data-server
-------------------------+----------------------
Reporter: gwhitney@… | Owner: devans@…
Type: submission | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: evolution |
-------------------------+----------------------
Comment (by gwhitney@…):
Replying to [comment:25 devans@…]:
> On the other hand, if you can build either with X11 support or Quartz
support then declaring both +x11 and +quartz is OK but you must declare
them as conflicting because you can't do both at the same time. Here -x11
is sensible because you CAN build without X11 support and the same for
-quartz.
Based on this it seems to me, the current implementation of a single
toggle +/-x11 captures exactly what is going on: evolution requires gdk
(indirectly via evolution-data-server) whether it is +x11 or -x11, but
evolution -x11 will compile on top of _any_ macports installation of gdk,
whereas evolution +x11 will only compile on top of gdk with the X11
backend and adds gnome desktop integration via the gnome-desktop port.
Isn't that just the right semantics for a single defined variant called
"x11"?
Anyhow no rush, looking forward to hearing how it's working for you and if
the X11-independent gcr looks reasonable to you. If so, I'd be happy
either to submit an upstream patch for that or to have you do so, since I
know that issue has been open for a long time in the gcr issue tracker.
--
Ticket URL: <https://trac.macports.org/ticket/52281#comment:27>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system
More information about the macports-tickets
mailing list