From owner-freebsd-hackers Tue Nov 5 14:34:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00576 for hackers-outgoing; Tue, 5 Nov 1996 14:34:38 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA00566 for ; Tue, 5 Nov 1996 14:34:33 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA06942; Tue, 5 Nov 1996 15:14:08 -0700 From: Terry Lambert Message-Id: <199611052214.PAA06942@phaeton.artisoft.com> Subject: Re: XFree86 3.2 now available. To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 5 Nov 1996 15:14:08 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199611052116.WAA26017@uriah.heep.sax.de> from "J Wunsch" at Nov 5, 96 10:16:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > One with the misc fonts.dir fixed so the JDK will "just work"? > > There's no ``fonts.dir'' fix generally applicable. > > The fonts from the `misc' directory have been split among various > packages for convenience. That's why you are _supposed_ to run a > mkfontdir after installation, and that's what the postinstall.sh > script of XFree86 3.2 does. (Only one out of 16 or so possible > installation cases will end up with the correct fonts.dir otherwise.) How about running it in the postinstall script for each of the packages it might affect, then? Also: the default fonts.dir could be made to not include the optional items by default, so that it *will* work by default. The only catch to doing it this way is that you may add fonts in a packages, and if they have bogus post-installs that don't do mkfontdir, the new fonts won't be available. Better that optional components not be available without user action than "unrelated" software fails to operate without user interaction. Fail safe or don't fail. Either way, it's still bogus to not do the mkfontdir as part of the package postinstall... it can be done, it should be done. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.