public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygapps <cygwin-apps@cygwin.com>
Subject: Re: [ITA] tcl-sqlite3
Date: Tue, 14 Jan 2014 12:56:00 -0000	[thread overview]
Message-ID: <CAO1jNwsK7uG99sShDhLkGAz=OvEwxSh7UXgMTdryV35Mr6Tnaw@mail.gmail.com> (raw)

2014/1/14 Corinna Vinschen:
> That's not what I meant.  What I meant is that Tcl extras are installed
> under /usr/lib/tcl, not directly under /usr/lib.  I have no idea about
> the TEA, but it looks wrong to install Tcl stuff to /usr/lib.  Perl
> stuff is under /usr/lib/perl, python stuff is under /usr/lib/python,
> ruby stuff is under /usr/lib/ruby... you get the idea.

Agreed. Then it's most logical to install in /usr/lib/tcl. I'll do that.

> 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.

No, I'm not implying at all that Fedora (or Cygwin) is wrong
at following TEA. TEA is designed to be able to install
multiple versions of Tcl extensions next to each other,
so if there are incompatible changes each Tcl application
can choose which one it wants. Sqlite3 is very careful
keeping upwards compatibility, so I would say
Sqlite doesn't need that. And I don't intend to support
multiple tcl-sqlite3 versions anyway. I have no problem
at all patching the TEA build scripts for that, just
as Fedora did.

Thanks!
        Jan Nijtmans

             reply	other threads:[~2014-01-14 12:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 12:56 Jan Nijtmans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-21 14:07 Jan Nijtmans
2014-01-21 16:26 ` Christopher Faylor
2014-01-14 15:50 Jan Nijtmans
2014-01-14 16:45 ` Corinna Vinschen
2014-01-14 19:30   ` Yaakov (Cygwin/X)
2014-01-14 19:49     ` Corinna Vinschen
2014-01-14 21:45       ` Yaakov (Cygwin/X)
2014-01-15  9:13         ` Jan Nijtmans
2014-01-20  3:52           ` Yaakov (Cygwin/X)
2014-01-20  9:37             ` Jan Nijtmans
2014-01-21 14:01               ` Corinna Vinschen
2014-01-14 19:48 ` Yaakov (Cygwin/X)
2014-01-14 12:15 Jan Nijtmans
2014-01-14 12:45 ` Corinna Vinschen
2014-01-14 20:34   ` Warren Young
2014-01-14 20:52     ` Corinna Vinschen
2014-01-14 21:39       ` Yaakov (Cygwin/X)
2014-01-13 10:57 Jan Nijtmans
2014-01-14  9:55 ` Corinna Vinschen
2014-01-14 19:16   ` Yaakov (Cygwin/X)
2014-01-14 20:39 ` Warren Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAO1jNwsK7uG99sShDhLkGAz=OvEwxSh7UXgMTdryV35Mr6Tnaw@mail.gmail.com' \
    --to=jan.nijtmans@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).