Thank you very much. Sorry, I did made the probably stupid assumption that an installation could and should always be done using the Kubuntu standard procedures.
Kubuntu has a large collection of installation procedures, which works very well for many stand alone softwares. Upgrades and occasionally urgent security bugs are managed in a very coherent way. tubogears is included in the proposed list from Kubuntu. I understand now that it is was bad idea for a complex package as Turbogears. Tomorrow I will start again with easy_install according to Turbogears recommendations. On Aug 1, 6:51 pm, Marco Mariani <[EMAIL PROTECTED]> wrote: > saliez ha scritto: > > [...] > > > * However I do not understand the UBUNTU philosophy about the > > management of external packages: > > I understand well they cannot provide full support for all external > > packages, particularly when they are continuously under developements. > > > The problem of the current version of KUBUNTU is that it do not yet > > install turbogears version 1.0.2.2, but only the 1.0 version, which > > is not compatible with python 2.5. Going back to 2.4 : > > I think you can use easy-install as a normal user (e.g. 'turbogears'), > and it would install everything (TG, kid, cherrypy...) in ~/.python_eggs > or something. > > Those packages would override the ubuntu ones for python sessions run by > that user. > > I've never done that, though. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
