From owner-freebsd-ports@FreeBSD.ORG Tue Nov 10 14:51:17 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F22D106566C for ; Tue, 10 Nov 2009 14:51:17 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.freebsd.org (Postfix) with SMTP id 899918FC16 for ; Tue, 10 Nov 2009 14:51:15 +0000 (UTC) Received: (qmail 20498 invoked from network); 10 Nov 2009 14:51:12 -0000 Received: from unknown (HELO ale.andxor.it) (192.168.2.5) by andxor.it with SMTP; 10 Nov 2009 14:51:12 -0000 Message-ID: <4AF97DDF.6090700@FreeBSD.org> Date: Tue, 10 Nov 2009 15:51:11 +0100 From: Alex Dupre User-Agent: Thunderbird 2.0.0.22 (X11/20090624) MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Subject: sqlite and tcl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2009 14:51:17 -0000 As you have seen, the up-to-date sqlite port requires tcl for *building*. A few of you complained about it, but I don't understand why you are not complaining about ports that have perl or python configure scripts, too ;-) Said so, I have a patch to switch the sqlite port to use the "amalgamation" tarball, which doesn't require tcl to build. The "only" drawback is that the tcl wrappers cannot be built/installed from such tarball. I'll not commit anything, but if you are using the sqlite tcl wrappers speak loudly and let us know. -- Alex Dupre