If python is built without USE=tk then zopeedit does not provide any dialog boxes on errors, and in some cases errors are not even reported to stderr (or anywhere). The example that alerted the problem to me was when saving the changes back to Zope fails. askRetryAfterError is called but just returns false. Perhaps this function or askRetryCancel should call fatalError if has_tk returns false. But the simple solution might be just to require that python is built with USE=tk. I don't know if portage provides a way to depend on python with USE=tk but built_with_use could at least check this is the case when zopeedit is installed.
A l337 patch... ;) --- zopeedit-0.9.1.ebuild.orig 2006-05-28 20:36:10.000000000 +0200 +++ zopeedit-0.9.1.ebuild 2006-08-17 07:48:40.000000000 +0200 @@ -15,6 +15,10 @@ #S=${WORKDIR}/${PN}-${PV}-src +pkg_setup() { + distutils_python_tkinter +} + pkg_postinst() { einfo "Please consider emerging also externaleditor zope product" einfo "Complete help available at: http://plope.com/software/ExternalEditor/install-unix/"
this was dropped
