On Sun, 5 Jan 2003 14:12:52 -0500
Jan Schaumann <jschauma@netbsd.org> wrote:

> I'm not so sure.  Why not check if Xft2 is installed, and if so, add the
> buildlink (thus depend on it) and otherwise disable Xft2 support?

Because it will generate different packages depending on the situation.
A variable is "better" (yes, the problem still exists, but this is likely
to be host-specific).

> Or maybe we need a variable USE_XFT2_WHEN_POSSIBLE (of course with a
> shorter name) so that any package that can work with and without Xft2
> can only use it if desired.

I'm working on a solution for this. The buildlink2.mk needs some magic,
because Xft2 does not compile under XFree86 3.x. The patch I'm writting
allows users to set USE_XFT2 in their mk.conf to specify if they want xft2
or not. This variable has no effect with XFree86 3.x, and can be tuned in
4.x. So any package that uses Xft2 will need to check for this variable.

I sent the patch to jlam for review yesterday, waiting for his answer ;)

Regards

-- 
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/