Date: Tue, 10 Nov 2009 10:06:44 -0500 From: Outback Dingo <outbackdingo@gmail.com> To: andrew clarke <mail@ozzmosis.com> Cc: ports@freebsd.org, Alex Dupre <ale@freebsd.org> Subject: Re: sqlite and tcl Message-ID: <5635aa0d0911100706p147521e7h415c920e60a8d3e2@mail.gmail.com> In-Reply-To: <20091110150302.GA49312@ozzmosis.com> References: <4AF97DDF.6090700@FreeBSD.org> <20091110150302.GA49312@ozzmosis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Actually i question why the extra tcl is even required. On Tue, Nov 10, 2009 at 10:03 AM, andrew clarke <mail@ozzmosis.com> wrote: > On Tue 2009-11-10 15:51:11 UTC+0100, Alex Dupre (ale@FreeBSD.org) wrote: > > > 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 ;-) > > In my case it was more a query about whether this new behaviour was > correct, since TCL was required regardless of the TCLWRAPPER toggle in > "make config", and I thought that was unusual. I have no strong > beliefs for or against TCL :-) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5635aa0d0911100706p147521e7h415c920e60a8d3e2>