Martin,
It is a bit extreme to say the Jeremy has gone
off the deep end with bleeding edge. Completely
untrue. Even if the X11 Xquartz was based entirely
on the same code as that in Snow Leopard X11, this
issue of potential incompatibilities would exist.
The change causing the problem is the movement of
X11 Xquartz into /opt. The reason he did that was
to prevent system upgrades from constantly nuking
the currently installed X11 Xquartz installation.
Also note that while X11 Xquartz 2.4.0 now contains
an automatic update mechanism, it isn't triggered
automatically after a system update has been
applied on Leopard to restore the previous X11
Xquartz installation's components. So short of such
a feature being added to X11 Xquartz, movement of
the X11 Xquartz installation to /opt is the only
way to prevent the system updates from overwriting
the X11 Xquartz components.
Jack
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
