[Pkg-tcltk-devel] Questions about backporting tcltk8.6; tdbc, drivers.

tomas at tuxteam.de tomas at tuxteam.de
Sat Jul 3 14:47:57 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Jul 02, 2010 at 07:50:06PM +0400, Konstantin Khomoutov wrote:
> On Tue, 22 Jun 2010 22:12:42 +0200
> tomas at tuxteam.de wrote:
> 
> > I have a couple of questions [...]

> After consulting with Sergei Golovan, I have decided to start packaging
> TDBC as a set of packages separate from tcl8.6 itself

Well, the version I got hold of (that's tcl8.6-8.6.0~b1) already builds a
separate TDBC .deb so that seems to be fine. Or did I misunderstand you?

>                                                       (in particular,
> I am personally interested in having MySQL and ODBC backends).

Heh. I'm interested in the PostgreSQL backend (tdbc::postgres). I've got
it now backported and running. Already stumbled upon what I think is a
bug, but that's to be expected this early.

> The ITP bug with some details about this packaging is available at [1].
> 
> The packaging is not finished yet.
> 
> I have somewhat uneasy feeling about this package, as there is no clear
> idea yet about how TDBC will be distributed when 8.6.0 comes out.
[...]

I see. Still I think the TDBC approach is very clean and it strikes a
very TCLish balance of simplicity and features -- so it deserves as much
exposure as it can get.

[...]

> upstream folks will decide to actually bundle TDBC into the Tcl's
> tarball. This issue has not been discussed with upstream yet but I
> intend to sort this out.

Why not just do different .debs off the same source, as it is done in
tcl8.6-8.6.0~b1?

> The current consensus between me and Sergei is to disable building
> of TDBC stuff packaged in the core Tcl tarball and keep TDBC separate
> for now.

Undeerstood. I lack the experience to understand the pros and cons of
that decision (but I trust you to take the right one ;)

> As to backporting -- I, personally, see no real merit of backporting
> 8.6 to Lenny for a number of reasons [...]

which are all valid -- but I can well imagine folks in my position: I'm
starting to play with Tcl/TDBC to see whether to write apps with that
next year or so. Of course, using a backport from unstable, I do know
that th world may change under me from time to time!

> When TDBC is packaged and Tcl 8.6 is re-packaged to exclude building of
> tcl8.6-tdbc, you will be able to backport both source packages to Lenny
> yourself if you want to; for stuff related to Tcl it is not really
> complicated anyway.

As mentioned in my last mail, I've a way to create a backport (I posted
a recipe, which ain't very beautiful, but might be useful for some). But
of course, I do look forward to a simpler and cleaner way to accomplish
that.

Thanks for your kind reply (and for all the hard work!), and let me know
whether I can be of any help (note that I'm not very dexter about Debian
packaging).

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFML02dBcgs9XrR2kYRAjJyAJ9ILbWgnq4DnUe221QV4p/DR2i2ygCfb4kN
ilJh/eAwHPS4fDeHFmii0pA=
=3mf3
-----END PGP SIGNATURE-----



More information about the Pkg-tcltk-devel mailing list