Bug#41690: [Image-SIG] Bug#41690: Ok, it now depends, but it shouldn't

[Fredrik Lundh]

Matthias Klose <doko@cs.tu-berlin.de> wrote:
>  > 1) link _tkinter with the tkImaging module (old style)
> 
> with the disadvantage of recompiling _tkinter.
> 
>  > 2) link _imaging with the same module (new style)
> 
> with the disadvantage of being forced to install all X11 and the Tk
> shared library (That's the way Lalo wants to use PIL).
> 
> 3) use the Tcl load extension to load the one PIL command. (does not
>    has the two disadvantages above).
>    But has the disadvantage that Tcl is set up correctly to handle
>    autoloading of packages.

after some fresh air, and some more digging, I've found
a fourth option, which should make everyone happy:

4) link _imagingtk with the tkImaging module

where _imagingtk is a new module, containing the tkinit
stuff from _imaging.  ImageTk should use this module to
activate the Tk interface.

to *build* the new module, you still need Tk and the rest
of the stuff, but it allows the package maintainer to ship
a single binary package.

expect a 1.0.1 release in a not too distant future...

</F>