> -- Original Message --
> From: Landry Breuil
> Date: November 14, 2019 at 3:21 AM
>
> Does this mean you're going to update/maintain this port again ? :)
>
> Landry
Yes.
Stu
On Thu, Nov 14, 2019 at 12:31:37AM -0500, 3...@bell.net wrote:
> Also I don't think this needs to be forced to build against 8.6.
Running the tests require 8.6 - and honestly, i'm only interested in
running the tests.
> Sorry for all the messages, I'm just coming back after almost 2 years
> away
Please keep them separate.
Much easier to update either.
If they were tied together and I wanted to update tcl-sqlite I'd have to
spend a week testing and convincing.
Also, tcl-sqlite isn't built with the same options as the main sqlite
port.
The tests would be nice but I'm not sure you're
"some of the SQLITE_ENABLE_XX choices look rather arbitrary."
Actually I spent some time carefully poring through all the options so I
could provide the best sqlite possible for Tcl.
Yeah, so separate please.
Stu
-- Original Message --
From: Landry Breuil
Date:
Also I don't think this needs to be forced to build against 8.6.
Sorry for all the messages, I'm just coming back after almost 2 years
away ... whatever that means.
Stu
-- Original Message --
From: Landry Breuil
Date: November 9, 2019 at 9:55 AM
Hi,
sqlite3-tcl is
On Sun Nov 10, 2019 at 10:37:07AM +0100, Landry Breuil wrote:
> On Sun, Nov 10, 2019 at 10:13:38AM +0100, Landry Breuil wrote:
> > On Sat, Nov 09, 2019 at 03:55:18PM +0100, Landry Breuil wrote:
> > > Hi,
> > >
> > > sqlite3-tcl is a bit outdated compared to 'main' sqlite3, so im
> > > pondering
On Sun, Nov 10, 2019 at 10:13:38AM +0100, Landry Breuil wrote:
> On Sat, Nov 09, 2019 at 03:55:18PM +0100, Landry Breuil wrote:
> > Hi,
> >
> > sqlite3-tcl is a bit outdated compared to 'main' sqlite3, so im
> > pondering moving back to the previous situation of having them as a
> > single port
On Sat, Nov 09, 2019 at 03:55:18PM +0100, Landry Breuil wrote:
> Hi,
>
> sqlite3-tcl is a bit outdated compared to 'main' sqlite3, so im
> pondering moving back to the previous situation of having them as a
> single port with multipackages (which was the case before sqlite3 got
> imported into
Hi,
sqlite3-tcl is a bit outdated compared to 'main' sqlite3, so im
pondering moving back to the previous situation of having them as a
single port with multipackages (which was the case before sqlite3 got
imported into base) - and while here i hacked my way around to be able
to run the tcl test
