Re: Xquartz version change?
Re: Xquartz version change?
- Subject: Re: Xquartz version change?
- From: Martin Costabel <email@hidden>
- Date: Thu, 06 Dec 2007 01:38:47 +0100
Jeremy Huddleston wrote:
[]
"need a specific version of X11" is antiquated. X11 is no longer
released as one monolithic package and hasn't been for a few years now.
This may be true in theory, but in real life my guess is that only a
negligible number of people will have chosen to pick different modules
from different releases. They will either have "Tiger's original X11" or
"Tiger's X11 with the 2006 updater" or "Leopard's original X11" or some
other complete package from xfree or xorg. In the case of Apple's
releases, the practical things to check are whether the user has also
the X11SDK installed which Apple unfortunately still distributes
separately, and whether the Apple installer has forgotten to install
some essential libraries or headers as it has a habit of doing.
As for non-existence of a monolithic package, is there still something
identifiable as "xorg release 7.2" or not?
Fink will need to adjust accordingly to "need a specific version of
libX11, libXft, libXt, etc, etc"... This is a "Good Thing". As an
analogy, saying you need X11 7.2 when you need libX11 is like saying you
need OS-X 10.3 when you need Carbon. The better thing to do is check
for Carbon.
Granted you want backwards compatability where appropriate, so I urge
you to do something like:
satisfiesLibX11Dependency() {
pkg-config x11 --atleast-version=1.0.3 && return 0
doThe10.4AndBeforeHacks()
}
As Peter has said, pkg-config is ruled out at the basic level where this
check is done, as long as Apple does not ship it with the system.
But anyway, this problem is not really serious, it currently only
concerns one easily fixable package.
--
Martin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden