Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Jun 2001 17:52:42 +0300
From:      Maxim Sobolev <sobomax@FreeBSD.ORG>
To:        Jean-Marc Zucconi <jmz@FreeBSD.ORG>
Cc:        ports@FreeBSD.ORG, portmgr@FreeBSD.ORG
Subject:   Re: XFree86-4 & freetype
Message-ID:  <3B1E43BA.97516BA0@FreeBSD.org>
References:  <20010606113816.C18735@ringworld.oblivion.bg> <200106060915.f569FPA01860@vega.vega.com> <200106061407.f56E7vU27744@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Jean-Marc Zucconi wrote:

> >>>>> Maxim Sobolev writes:
>
>  > It is already known that XFree86-4 installs incomplete version of
>  > freetype2 which creates number of weird problems.
>
> I already stated that XFree86-4 does no install an incomplete version
> of freetype2. This is freetype2 which is broken. The ports using
> freetype2 are broken too.
>
> X11 has always used Imake to build programs and libraries. This is the
> rule and all X11 software must use it. This is why freetype2 is
> broken: it uses configure and libtool instead of Imake. Unfortunately
> ports depending on freetype make the same mistake, leading to the need
> of extra stuff like the config scripts. The right thing would be to
> ask the porters to fix the build process.

This is very XFree-centric point of view. Freetype is only complete in the configuration
provided by the freetype developers, if XFree86 developers think that some pieces of it are
redundant and thus could be stripped, then it is problem of XFree86, not freetype.

> Well, in the meantime we have to live with that but all problems can
> be avoided:
> - ports just requiring libfreetype.so (using -lfreetype in makefile):
>   they need a LIBDEPEND=freetype.6:${PORTSDIR}/print/freetype2. If
>   make detects an installed library in /usr/local or in /usr/X11R6 it
>   will work with either one thanks to our loader lazyness. If X11 is
>   not installed (or if it is XFree-3, or if XFreee-4 was installed w/o
>   freetype support) print/freetype will be installed.
> - ports requiring the freetype config script:
>   they need another depend: BUILD_DEPENDS= freetype-config:${PORTSDIR}/print/freetype2.
>   in this case the port will be installed and because of the script it
>   will be explicitly linked with the print/freetype lib.

This is an ugly hack. I could provide at least several reasons why it is wrong, but do you
really care? The only way the problem could be solved properly is to use external freetype
library instead of one bundled with XFree86 during XFree86 build. There is very little work
involved, because XFree86 developers even provide special configuration knob for that.

Jean-Marc, you are trying to convince us in the things in which you do not believe. IMO,
the only reason you don't want to use external freetype library is your misbelief that the
XFree86 is thing in itself and thus should not depend on any external package. This
position is wrong, because there is nothing special in the XFree86 - it is just a big
software package that where appropriate could and should use components provided by other
packages.

-Maxim


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B1E43BA.97516BA0>