Prev: is there a lightweight markup language rendering engine usingtext widget
Next: is there a lightweight markup language rendering engine using text widget
From: Alan Grunwald on 18 Jun 2010 12:10 AndreasK wrote: > On Jun 17, 10:33 am, Alan Grunwald > <alan.via.a...(a)nurdglaw.demon.co.uk> wrote: >> Andreas Kupries wrote: >>> Alan Grunwald <usenetReader_NOSPAM(a)NOSPAM_nurdglaw.demon.co.uk> >>> writes: >>>>> Apparently the tdbc* packages use tcl_findLibrary to find their .tcl >>>>> code, and get confused by the directory names used by the repository. >>>>> I am in the process of fixing that. If the build this night went ok I >>>>> might even have binaries for you to test. >>> The TDBC packages in the TEApot have been updated to forms not >>> requiring tcl_findLibrary. Alan checked those which he needed, and >>> they work. >>> The build date of the fixed packages is >>> as::build::date : 2010-06-14 >>> Their version (1.0b15) is unchanged. >>> Kevin has the changes I made, for integration with his mainline. >>>>>> I then tried to verify my teapot with >>>>>> sudo /opt/ActiveTcl-8.6/bin/teacup verify >>>>>> This displayed >>>>>> Checking /opt/ActiveTcl-8.6/lib/teapot ... >>>>>> Bad version "tcl1.0" >>> The new package >>> dbus-tcl1.0 >>> added a few weeks ago tripped the verify's handling of dashes. The >>> teacup binaries now in the TEApot have the problem fixed. >> Thanks Andreas, >> >> I can confirm that the updated teacup works fine. I can also >> confirm that I tested Andreas's modified tdbc drivers and tdbc::mysql >> (the only one I use) works fine. However, my 'teacup update' just now >> didn't bring down a new copy of tdbc and drivers, and I don't know how >> to force a download, so I can't verify that they are in the teapot. > > teacup install --force ... > > or 'teacup remove the-package' followed by 'teacup install' > > Note the 'teacup help install' command for cmdline help. > > Thanks Andreas teacup install --force tdbc::mysql brought down new copies of tdbc and tdbc::mysql (and TclOO!) which works fine, so I can confirm that an updated, working tdbc::mysql is indeed in the teapot. -- Alan
From: lowclouds on 22 Jun 2010 20:31 On 6/10/2010 6:11 AM, Andreas Kupries wrote: > Alan Grunwald<alan.via.aioe(a)nurdglaw.demon.co.uk> writes: > >> A fresh tclsh already has TclOO 0.6.1 present > > Ah. You are running an older Tcl 8.6, which has TclOO built in. I > thought that you were running an 8.5 where you have to require it. > I'm in a similar muddle that Alan was in and want to know how I should manage teacup repositories with multiple concurrent versions of tcl, in this case 8.5x and 8.6b1.1. should i set up two repositories and hook them up to the different tclshs or can one repository manage all my tclshs? thanks, craig >>>> How can I get my tdbc::mysql back? > >> I've been beating myself up about this since I got up this morning. I >> think the answer is that yo shouldn't post about problems late at >> night. >> >> I am currently running ActiveTcl8.6.0.0b1 - info patchlevel returns 8.6.1b1. > >> I strongly suspect that version has TclOO 0.6.1 built in to tclsh and >> that I need to upgrade to the latest ActiveTcl8.6.0.0b3. I'm doing >> that now and will report back on how that pans out. > > Ok. >
From: Andreas Kupries on 1 Jul 2010 14:37
lowclouds <xyz(a)nowhere.net> writes: > On 6/10/2010 6:11 AM, Andreas Kupries wrote: >> Alan Grunwald<alan.via.aioe(a)nurdglaw.demon.co.uk> writes: >> >>> A fresh tclsh already has TclOO 0.6.1 present >> >> Ah. You are running an older Tcl 8.6, which has TclOO built in. I >> thought that you were running an 8.5 where you have to require it. >> > > I'm in a similar muddle that Alan was in and want to know how I should > manage teacup repositories with multiple concurrent versions of tcl, > in this case 8.5x and 8.6b1.1. should i set up two repositories and > hook them up to the different tclshs or can one repository manage all > my tclshs? A single teapot repository can handle multiple versions of Tcl / tclsh's. This is also under your control. If you install both ActiveTcl's into the same directory they will share the repository made by the installer. If you install the distributions into different directories they will get separate repositories. -- So long, Andreas Kupries <akupries(a)shaw.ca> <http://www.purl.org/NET/akupries/> Developer @ <http://www.activestate.com/> ------------------------------------------------------------------------------- |