From owner-cvs-all Tue Feb 4 9:19: 7 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23AC337B405; Tue, 4 Feb 2003 09:19:05 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A4E443F85; Tue, 4 Feb 2003 09:19:04 -0800 (PST) (envelope-from mi+mx@aldan.algebra.com) Received: from mi.us.murex.com (250-217.customer.cloud9.net [168.100.250.217]) by corbulon.video-collage.com (8.12.7/8.12.7) with ESMTP id h14HIwM5065733 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Tue, 4 Feb 2003 12:19:03 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Content-Type: text/plain; charset="koi8-u" From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Eric Anholt Subject: Re: cvs commit: ports/x11/kdebase3 Makefile Date: Tue, 4 Feb 2003 12:19:24 -0500 User-Agent: KMail/1.4.3 Cc: Alan Eldridge , cvs-committers@freebsd.org, cvs-all@freebsd.org References: <200302031235.h13CZwGB073669@repoman.freebsd.org> <200302031408.14342.mi+mx@aldan.algebra.com> <1044378636.615.10.camel@leguin> In-Reply-To: <1044378636.615.10.camel@leguin> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200302041219.24215.mi+mx@aldan.algebra.com> X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 04 February 2003 12:10 pm, Eric Anholt wrote: = It would be best if QT could use Xft2, as that's the future. In stock = XFree86 4.3, Xft1 programs compiled against it use the Xft2 library. = The backwards compatibility is not perfect, so for now we will = continue to have libXft2.so.2. In stock XF86, it's called libXft.so.2 = and there's a binary-compatible Xft1 library at libXft.so.1 which = nothing new ends up using. The current XFree86 4.3-pre ports I'm = working on continue with the libXft2.so.2 system we've had. I'm sorry, could you elaborate on the advantage of libXft2.so.2 over the libXft.so.2? I understand, that the older binaries need the libXft.so.1, but why call the new version libXft2? This will force us to patch a lot of things (starting with Qt)... If it is for compatibility with something we already shipped, how about symlinking libXft2.so.x to libXft.so.2? = Hopefully by the time 4.3 hits the tree we'll have the Xft1 programs = with problems converted to Xft2 or fixed, so they can work without the = renaming of libraries/includes that we currently do. = The Xft2 port will continue to exist. I think the more we keep these = libraries split from being a monolithic build, the better. Agreed -- if it means, the XFree86-4-libraries (or -clients) will depend on it -- like it does on freetype2 -- instead of building its own :-) Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message