[EMAIL PROTECTED] schrieb: > First, we should decide a way to 'list available quickstart templates' > for future version > Is it ok to point out the usage in doc, or implemented as a wrapper > around that as jorge.vargas suggestion in trac? > > I prefer the prior one as we discussed about the nosetests wrapper.
I think it would be better to restrict the list of templates to TG specific ones, hence we may need a wrapper. > Third, should we separate all quickstart templates as extensions? +1 but I also think that we should not increase the number of separate packages that need to be downloaded without need. Is there a way to include an extension into the TG egg itself? > Forth, if we think so, what is the preferable way to organize the > increasing projects in trac? This also affects the maintenance of the list of requirements for a TG install. Would we need "distribution package lists" for different requirements for a basic/database-enabled/full-developer install? Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
