From owner-cvs-user Sat Apr 12 10:28:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA12143 for cvs-user-outgoing; Sat, 12 Apr 1997 10:28:50 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12134; Sat, 12 Apr 1997 10:28:42 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA03690; Sun, 13 Apr 1997 03:22:10 +1000 Date: Sun, 13 Apr 1997 03:22:10 +1000 From: Bruce Evans Message-Id: <199704121722.DAA03690@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@spinner.DIALix.COM Subject: Re: cvs commit: src/lib Makefile Cc: cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-user@freefall.freebsd.org, nate@mt.sri.com Sender: owner-cvs-user@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Can it be built to use tcl if tcl is gone at build >> time but present at run time? > >I'd rate that as "you couldn't count on it". There might be a libtcl in >the library path, and the includes might still be around, but it'd >be at the risk of running into stale stuff. I presume this is what you >meant? (ie: src/contrib/tcl missing, but otherwise installed on the system) No, I meant "what happens if tcl is completely gone?". Are people supposed to rebuild vi to get tcl support? Bruce