From owner-freebsd-current Tue Jan 4 8: 8:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id EF55215355 for ; Tue, 4 Jan 2000 08:08:20 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 125WVI-000FXa-00; Tue, 4 Jan 2000 16:08:12 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id RAA05982; Tue, 4 Jan 2000 17:08:11 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38721AEB.68D35958@scc.nl> Date: Tue, 04 Jan 2000 17:08:11 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > > > It uses wrong ifdefs for the X11 files :-). It should never find any X11 > > > files for building worlds, since there are no X11 includes or libraries > > > under ${WORLDTMP}. Adding some ${DESTDIR}'s is probably a sufficient fix. > > > > Ok, but this means that we won't install doscmd with X11 support > > anymore. The user has to rebuild doscmd itself to have X11 support. In > > This is nothing new, I hope. The release build environment shouldn't be > polluted with X11, so releases should only have non-X11 doscmds. Duh... that's probably the case because a release is built in a chrooted environment. A buildworld/installworld will behave differently though. I don't know if there're people that depend on world to install a doscmd that has x11 support? > > that case, it's better to have it in the ports collection... > > I think it's too system-dependent to work well as a port. I think it's too system dependent to live in the source tree :-) From the manpage: -x Open an X11 window to display output. This enables a variety in- terrupts not available otherwise. Simply compiling with X support also isn't enough, because the default font (vga) is not present in a default X installation. Ergo: doscmd won't run in a X window unless you grab a compatible font from the net. > You would need 2 ports, one with X11 support and one without. But isn't that what our ports collection isn't all about. Examples: kde11 vs kde11-i18n nethack vs nethack-qt *emacs* Alternatively, the user can specify whether he/she wants X11 support by adding -DUSE_XLIB or -DNO_X or whatever. Not to forget that we can also use NetBSD's port! -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message