> This isn't a good approach. It will lead to problems when people deploy their > applications and don't know exactly what they need to have along > with "turbogears-essential" (I renamed it to make it clear it is a bare > package) to replicate their production environment. > > It is better to document things and explain to them how to install add-on > packages.
We clearly need to document stuff, so people can determine what to install, but we also need to make getting the easy-start-up tools easy. And frankly if people install the toolbox on their server it should not actually hurt anyone. If it does, we've done something wrong. Packages which aren't used shouldn't be imported -- so the worst case thing is that there are a few hundred kb of extra python source code taking space on the hard drive. What if for turbogears 2 we create a tg package which is the minimal install, a tg-dev package which depends on tg, and provides all the "standard" extra tools. Then we can foucus our "easy-startup" documentation on the tg-dev package, but also have a page explaining what all is installed and how to install things package by package. People should also be able to create their own "dependency" lists for their applications, and we should tell them how to use that feature of the quickstarted template. By default our template shouldn't depend on dev, but on the tools that are needed by the quickstarted app. If we create identitiy included templates, those should add identity to the setuptools requirements in the paster template automatically. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
