Date: Sat, 02 May 1998 16:44:53 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: bjc23@hermes.cam.ac.uk Cc: dwilde1@ibm.net, advocacy@FreeBSD.ORG Subject: Re: A GUI greyscale interface by default Message-ID: <25309.894152693@time.cdrom.com> In-Reply-To: Your message of "Sun, 03 May 1998 00:04:58 BST." <Pine.BSF.3.96.980502235900.241a-100000@bjc23.trin.cam.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Um. Making this work would be trivial than you think. Interaction with the user, specifically, is something that would be difficult from within sysinstall's current framework given that all I/O goes to a different screen than the one the user is generally looking at. There are a host of other issues as well and anyone wishing to tackle them in sysinstall can be my guest because I don't particularly feel like trying to make it work. :-) - Jordan > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25309.894152693>