<div dir="ltr">answering to James first<div><br></div><div>> <span style="font-size:12.8px">Wayland offers the same disadvantages as quartz ... try to sell you argument to </span><a href="http://ltsp.org/" rel="noreferrer" target="_blank" style="font-size:12.8px">http://ltsp.org</a></div><div><br></div><div>so, here we are talking about Darwin as the target for GTK3 and WebKit2GTK via MacPorts.</div><div>What should I sell to ltsp exactly I've no idea, also I think is really out of scope.</div><div><br></div><div><br></div><div>Answering to Mojca, I do have a Mac Mini 2010 Dual core 2.4Ghz + 8GB of RAM. It's not the fastest machine on earth but it works and it's lying around.</div><div>If it has to build 24/7 it's OK but I don't know how to configure it or what exactly should I do to contribute.</div><div><br></div><div><br></div><div>Best Regards</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 9, 2016 at 9:00 AM, Mojca Miklavec <span dir="ltr"><<a href="mailto:mojca@macports.org" target="_blank">mojca@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 8 May 2016 at 11:19, Andrea Giammarchi wrote:<br>
> Like I've said, telling users they need to wait at least one hour to<br>
> install and build gtk3 +quartz and webkit2-gtk +quartz due lack of pre built<br>
> version<br>
<br>
</span>There are two options:<br>
(i) Switch the default from x11 to quartz<br>
(ii) Provide binaries for both x11 and quartz<br>
<br>
The first option is problematic because a lot of software doesn't work<br>
without X11 (assuming that GTK implies X11). If MacPorts switches to<br>
Quartz, all that software will be broken and it would be even more<br>
pain to explain to users that they need to switch to X11 just to get<br>
the software from a broken state to a working state (and they would<br>
also have to compile equally long). Now only those who want a better<br>
user experience have to switch.<br>
<br>
In theory there is also:<br>
(iii) allow co-existing support for quartz and x11 (at least for gtk3;<br>
I'm sure this is not possible for wxWidgets for example)<br>
<br>
So at the moment we could consider different options for (ii). These<br>
are for example:<br>
<br>
(a) Provide support for resolving dependencies automatically (some<br>
work has been done during GSOC 2015, but it has not been finished<br>
yet). Then the required binary packages would be built automatically<br>
on the buildbot (as soon as one package would request "gtk3 +quartz").<br>
<br>
(b) Provide more hardware to set up a separate buildbot with "+quartz"<br>
being set by default. This means 6 additional virtual machines running<br>
on Apple hardware. That's not trivial, at least not at the moment.<br>
(Does anyone have extra hardware lying around? It has to be reasonably<br>
fast to catch up with all commits though. If so, we could in principle<br>
play with an unofficial buildslave building packages for +quartz.)<br>
<br>
(c) Modify the existing buildbot setup to perform (very) dirty tricks<br>
to build support for +quartz (for example: build packages, deactivate<br>
them, modify the default variants to add +quartz, build packages<br>
again, deactivate them, set the default flags back).<br>
<br>
It's also true that if binary packages for Quartz were supported,<br>
there would probably be more incentive to fix the broken software.<br>
<br>
<br>
But unless you have concrete solutions for any of the points mentioned above ...<br>
<span class="HOEnZb"><font color="#888888"><br>
Mojca<br>
</font></span></blockquote></div><br></div>