From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21215 invoked by alias); 14 Jan 2014 20:52:56 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 21195 invoked by uid 89); 14 Jan 2014 20:52:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Jan 2014 20:52:55 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 4DEEA1A0A30; Tue, 14 Jan 2014 21:52:52 +0100 (CET) Date: Tue, 14 Jan 2014 20:52:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [ITA] tcl-sqlite3 Message-ID: <20140114205252.GG10212@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20140114124456.GA10212@calimero.vinschen.de> <52D59F6A.6050505@etr-usa.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uc35eWnScqDcQrv5" Content-Disposition: inline In-Reply-To: <52D59F6A.6050505@etr-usa.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-01/txt/msg00049.txt.bz2 --uc35eWnScqDcQrv5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1245 On Jan 14 13:34, Warren Young wrote: > On 1/14/2014 05:44, Corinna Vinschen wrote: > > > >Also, even if sqlite3.8.2 and sqlite382.dll works, it's kind of > >puzzeling. Are you saying using sqlite3 and libtclsqlite3.so on Fedora > >is wrong, not following TEA? It's much easier to grok and doesn't > >wrongly imply it only works on a specificx sqlite 3.x.x version, IMHO. >=20 > Yaakov makes a good point: the whole idea of tcl-sqlite is that it > wraps the SQLite 3 API exactly, so when new public APIs get exported > by SQLite, new APIs appear in the Tcl wrapper. Therefore, a new > version of tcl-sqlite really *could* depend on a specific version of > SQLite, if the API changed. In how far does that affect the filename? We're adding new APIs to Cygwin all the time, but the DLL is still called cygwin1.dll. And that's how it works for any other DLL as well as long as it doesn't break backward compatibility, API-wise. It's your and Yaakov's call eventually, so I retract all my idle musings in terms of the file or directory names. Just let Jan know how you want to have it. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --uc35eWnScqDcQrv5 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJS1aOkAAoJEPU2Bp2uRE+gGacP/i6thamzcoh1npRR2ZmaVLLD WniKroB/ajQdNa2qulr+ajGAjEn7uUu9c70Ekf1BmgYc558ODC2Xw5IQVRNL2Mkt N1FnSbcBYNTJL1ENypR9THhRKP2YFHjAMw9rAHEUg2Gkcv6QcrakKknwmlxJHr0K 5EULhSpuqRJcAk6ftYYtZjktSOWjSDZNKnFCYoyXQX7XZJsjHfReFpRb6uyCr3+t ep9sTHzJyRAsnmqsCh+HdO08OfSvWKESzuUTT3t5VuJMTx9be8NhmMU5PXVdeSxy IVMDWGMroGl1KC/qFnmQevcjGT/lke5Zi3mNtn7hhAMmcoPluOIc594wfVDvVSgu ev2OthJzgxwfZwq4p9XWxaCvGNsuNLirOSbs3dzIjX6pok8tEkwCM3jl132o4ceO kxxOMQ10xd4VmISR6KXaKn3QBdPCl4f8zrnPrRTA4J2fLX9n21g+f+dfHHUBBak/ iMnFz7IvevD5ool8e+AVC8W7HuMCRwj6/vNkxPyRkuf7RaP3fSc61CUlXtPgQGpG dKhoBEfLwDQJEWwijAH1ZoFX+v+t2topplWT4Eda259SoKx2m/ypjZvt4TnfNr+9 wbirTcDWUafzzwxJKgq+5HTxQF+rjclUcwWZW/ENvF88EdeLAI1d7gMlCKpmMHhM YrW/YkFmJOKclOJgewty =vTtR -----END PGP SIGNATURE----- --uc35eWnScqDcQrv5--