From: L J Bayuk <ljb220@mindspring.com>
Message-Id: <200402240247.i1O2l9oO005121@mindspring.com>
Subject: Re: tcl on gborg, pgtclsh
To: scrappy@postgresql.org (Marc G. Fournier)
Date: Mon, 23 Feb 2004 21:47:09 -0500 (EST)
Cc: peter_e@gmx.net (Peter Eisentraut),
	pgsql-interfaces@postgresql.org, xgbe@yahoo.com (Chris Ryan)
In-Reply-To: <20040223121517.B48887@ganymede.hub.org> from "Marc G. Fournier"
	at Feb 23, 2004 12:16:01 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Marc G. Fournier wrote:
> 
> On Mon, 23 Feb 2004, Peter Eisentraut wrote:
> >
> > Note, if you move libpgtcl elsewhere, you will also have to take pgtclsh
> > and pgtksh with it.  Currently, I don't see these programs in the pgtcl
> > project on gborg.  Also, don't forget to move the documentation this
> > time.
> 
> Good points, thanks ... LJ, any chance you'd be willing to 'maintain'
> these on gborg?

Yes and no.

I do have pgtclsh and pgwish (which I renamed from pgtksh) in my project.
They build and test OK, but I moved them to an "extra" directory, labeled
them as "deprecated", and do not provide auto-configure.  Also, I won't
include support for building them on Windows.  In my opinion, it's so much
better to use dynamic package loading with Tcl, that it makes no sense to
link a specific extension into a Tcl shell anymore.  "package require
Pgtcl" is the way to go. But if anyone really needs the pg* shells, they
can edit a few lines in the Makefile and build them.

However... shortly after I created a new project on Gborg for my version of
the Tcl interface, the original Gborg pgtcl project started getting
updates. I don't know what Brett's plans are, but I'm in a quandary about
what to do. I'm very close to finishing up my version, including the new
reference manual and Windows binary release, but I've held off uploading or
releasing anything. I didn't count on forking an active project, and I
don't want to do the wrong thing. Advice?