From owner-freebsd-advocacy Sat May 2 16:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02022 for freebsd-advocacy-outgoing; Sat, 2 May 1998 16:05:16 -0700 (PDT) (envelope-from owner-freebsd-advocacy@FreeBSD.ORG) Received: from violet.csi.cam.ac.uk (exim@violet.csi.cam.ac.uk [131.111.8.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01994 for ; Sat, 2 May 1998 16:05:09 -0700 (PDT) (envelope-from bjc23@hermes.cam.ac.uk) Received: from bjc23.trin.cam.ac.uk ([131.111.212.250]) by violet.csi.cam.ac.uk with smtp (Exim 1.92 #1) id 0yVlKx-0003MR-00; Sun, 3 May 1998 00:04:55 +0100 Date: Sun, 3 May 1998 00:04:58 +0100 (BST) From: Ben Cohen X-Sender: bjc23@bjc23.trin.cam.ac.uk Reply-To: bjc23@hermes.cam.ac.uk To: "Jordan K. Hubbard" cc: dwilde1@ibm.net, advocacy@FreeBSD.ORG Subject: Re: A GUI greyscale interface by default In-Reply-To: <24978.894148963@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > level first, before we even begin to talk GUI. For example, while > > installing printing, I discovered that /stand/sysinstall is completely > > blind to the /usr/ports/print branch of the ports tree. This means it > > can't find ghostscript, freetype, etc., and therefore crashes. We need > > Huh? Sysinstall has NO implicit knowledge of the ports tree and never > has had. What are you even talking about here? It would be handy (wouldn't it?) if the packages part of /stand/sysinstall could also understand the ports tree and be able to manage installation of ports and other packages. This _should_ be possible because the ports tree has a sensible structure: nothing much really needs to be hard-coded into the program because it can extract the information it needs from the HTML files there and /usr/ports/*/pkg/DESCR. Ben. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message