I'm actually not using turbogears per se, but many of the same components, on gentoo in production. I have an overlay that is partly based on some ebuilds by a gentoo developer (who might not want the attention so I won't name him, but you can find him on #gentoo-python, I bet!) which do *not* use the eggs approach, but use the single-version-externally-managed route. Since I believe that that option becomes default when --root is specified in later versions of setuptools, this becomes pretty trivial and the standard distutils eclass may already work with setuptools-based packages. I'd recommend this approach.
My overlay has: cheetah kid psycopg pysqlite ruledispatch sqlobject elementtidy mysql-python pydo pysyck simplejson formencode nose pyprotocols routes skunk If anyone wants access to it, just send me an email. j --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
