From owner-freebsd-config Mon Mar 3 23:37:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA03407 for config-outgoing; Mon, 3 Mar 1997 23:37:43 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03402 for ; Mon, 3 Mar 1997 23:37:41 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA21303; Mon, 3 Mar 1997 23:37:27 -0800 (PST) To: Michael Smith cc: erich@lodgenet.com (Eric L. Hernes), msmith@gsoft.com.au, freebsd-config@FreeBSD.ORG Subject: Re: Psst! TurboVision? In-reply-to: Your message of "Tue, 04 Mar 1997 15:28:17 +1030." <199703040458.PAA10574@genesis.atrad.adelaide.edu.au> Date: Mon, 03 Mar 1997 23:37:26 -0800 Message-ID: <21298.857461046@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-config@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is my problem too. I've been trying to work out a good interface > from Tcl to Tvision; TV still wants lots of its stuff configured at compile > time from what I can read of the examples. Like I said, my take at this has been to write everything at a high functional level in C++ and TV, providing large functional blocks like "configure network device" or "open media" which are then exported into TCL so that you can use it as a true scripting language to control installation flow. You wouldn't write the whole install in TCL with infinite extensibility (as some of us might have envisioned), just use it to control the whole "novice/expert/custom" install paradigm and provide hooks for command-line invocation of installation "configlets" Jordan