Install fails because _tkinter.so is not found.  This
library is not built if the tk header files are not
found, but the installer treats this as a fatal error.
 This dependece upon tk-devel is not noted in the .spec
file, so the install fails late (and unclearly) instead
of early & clearly.

Logged In: YES 
user_id=33168

Note: we don't maintain 2.3 any longer.

Sean any comments?

Logged In: YES 
user_id=81797

The build doesn't really have a way of adaptively adjusting
to whether Tk is available or not.  Some people in the past
have wanted to build without tk, but perhaps we should just
always build with tk?  Also, newer RPM versions have a nicer
way of doing conditional builds which will probably help this.

Any ideas?  I'll try to get a new release of the spec file
out in the next week and build some SRPMs from them so that
people can try them.

Currently, this is only addressed by being a FAQ on the RPM
pages.

Sean

I'm going to call this closed because this is basically a build
environment problem and the RPM can't really detect it at build time. 
This is noted in the RPM building FAQ, and if you search for the
"unclear" message you will find the resolution (either installing the TK
development package or removing the TK runtime package, depending on
your exact needs).