Comment # 12
on bug 10640
from Guy Harris
(In reply to Andreas Fink from comment #10)
> 1. X11 is no longer part of OS X since release 10.7. We are having 10.10
> today!
> Its like if you would say, you build it for Debian release 5 and it works
> under Debian 5 but its broken in Debian 8 but you won't fix it.
Linux distributions aren't as nice as Apple when it comes to backwards binary
compatibility. With XQuartz, Apple made an effort to support backwards binary
compatibility by planting the /usr/X11 symbolic link; unfortunately, the
developers of the Yosemite installer screwed up and failed to preserve that
symbolic link.
> 2. Today >90% of OS X users use 10.10 (see example here:
> http://update.omnigroup.com)
So? Why should we screw over people using older releases (for whatever reason,
be it "the hardware won't support the newer OS" or "my iPhone won't support
anything newer than iOS 3 and thus won't support iCloud but I still want to
sync my iPhone with my Mac" or "I want to make damn sure that the video driver
doesn't screw up even worse with the new release than it does with Mountain
Lion" or "discoveryd sucks" or whatever) if we can avoid that?
> 4. The problem could be easily fixed by
>
> - have a version for up to 10.7 with X11 and a version for 10.8 and above
> using XQuarz.
It's bad enough that we have separate 32-bit Leopard and 64-bit Snow
Leopard-and-later versions, although 1) Leopard's BPF is broken with 64-bit
binaries so a fat version would have to work around that and 2) GLib *really*
makes it painful to build it fat, so that's a bit more work.
Further separating versions would be a bit too much.
> or
>
> - have a post install script which simply fixes the dependencies by calling
> install_name_tool <oldlibpath> <newlibpath> <binary/or lib to fix>
That doesn't fix the problem for people who upgrade to Yosemite. It worked
fine for me on a freshly-installed Yosemite system on which I installed XQuartz
and Wireshark; it didn't work on a pre-Yosemite system on which I'd installed
XQuartz and Wireshark when I upgraded it to Yosemite.
> The proper fix is not to do a symlink from /usr/X11 to /opt/X11.
Apple disagrees with you on this, given that the XQuartz installer installs
that symlink, and I think Apple are correct and you are incorrect here.
> The proper
> fix is to refer to the correct libraries in the right path during build time
> and the XQuarz libraries do in fact have the path /opt/X11 built into them
> which means your build process is running on a outdated machine
Our build process is running on Lion with a version of Xcode that supports the
Snow Leopard SDK, to make it easier to build a version that'll run all the way
back to Snow Leopard.
> If you don't support XQuarz then you don't support 10.8, 10.9, 10.10. Then
> please say so on the webpage so people don't download a version they can't
> use.
We *do* support XQuartz, because one of the components of XQuartz is a symbolic
link from /usr/X11 to /opt/X11. What we need to do is, as per my comment,
unbreak the XQuartz installation if the Yosemite installer broke it.
> It did properly work on the previous version (1.12.2) and now you break it
> in 1.12.4 again.
We changed nothing in 1.12.4.
You are receiving this mail because:
- You are watching all bug changes.
