From owner-freebsd-ports Mon Apr 9 9:12: 1 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D065137B422; Mon, 9 Apr 2001 09:11:56 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f39GBoI73283; Mon, 9 Apr 2001 13:11:51 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Mon, 9 Apr 2001 13:11:50 -0300 (ADT) From: The Hermit Hacker To: Maxim Sobolev Cc: Ade Lovett , Subject: Re: Imagemagick doesn't know about freetype2 ... In-Reply-To: <3AD1DA69.41F7B257@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 9 Apr 2001, Maxim Sobolev wrote: > Ade Lovett wrote: > > > On Sun, Apr 08, 2001 at 01:17:37AM -0300, The Hermit Hacker wrote: > > > > > > subject pretty much says it all ... even though its a dependancy? > > > > This is a known problem. XFree86 4.mumble, in it's infinite wisdom, > > includes freetype2 (it used to be worse - only bits of it), however, > > the current incantation misses out the rather useful 'freetype-config' > > script. > > > > Adding -I${X11BASE}/include/freetype2 to the CONFIGURE_ENV line in > > the Makefile is one way around it. > > > > The other is to clean up the whole freetype2/XFree86-4 mess. > > Unfortunately jmz doesn't show any willingness to do a messcleaning, so > 4.3 is likely to be shipped with this nasty bug. :-( Okay, I might be missing something, but why is shipping freetype2 with XFree86 a bad thing? Just cause it doesn't do the freetype-config script? If so, can't it be added to the port itself? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message