From owner-freebsd-hackers Tue Dec 8 18:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19705 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 18:51:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19700 for ; Tue, 8 Dec 1998 18:51:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA18400; Tue, 8 Dec 1998 18:51:02 -0800 (PST) To: Allen Campbell cc: hackers@FreeBSD.ORG Subject: Re: sysinstall In-reply-to: Your message of "Tue, 08 Dec 1998 13:27:31 MST." <199812082027.NAA24541@bamboo.verinet.com> Date: Tue, 08 Dec 1998 18:51:01 -0800 Message-ID: <18396.913171861@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What bits, if any, of sysinstall's successor are currently available? I > have read in -hackers and -commit about the desire to replace > sysinstall. I thought I had read that Mike Smith was currently working > on this. Mike, I and Eugene (a contractor in Russia) are working on it. What we've decided to do is start with the new package system since the idea has always been that sysinstall would be little more than a wrapper around a much more powerful packaging system which handled all the dependency, registration and upgrade functionality. Sysinstall itself would do little more than set up disks and figure out how to get packages from a wide variety of media. In any case, the new package system is still very much a WIP and also has some pretty hefty prerequisites: Qt 1.40 or later. TurboVision 0.6 or later. gcc 2.8.1 or later (also including egcs). The latter is the biggie for most folks since 2.7.2, our current compiler, has C++ support which is broken in too many ways for Eugene to write the kind of C++ code he wanted to write (he's a big fan of templates and MI). Since we've wanted to upgrade our compiler toolchain for some time, I figured this was as good a justification as any and am still looking for a team to jump in with egcs 1.1.1 and start looking at the integration issues. Both Poul-Henning Kamp, John Polstra and Peter Wemm have looked into this a bit already but time constraints will probably prevent any of them from doing anything more substantive than that for awhile. In other words, people are welcome to jump in on this one! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message