On Aug 24, 4:43 pm, Jonathan Vanasco <[email protected]> wrote: > i have a different approach... > > i keep all the shared templates in its own repository, which is put > into each project as an svn:external > > the projects then use a standard config file to either use the shared > template or an override in their own directory structure > > i could have used a file exists check, but i felt a config option > would be more extensible
Thanks, that's another option to keep in mind. I hadn't thought about using SVN that way. Does keeping it all in sync get tricky as the number of different pylons apps that hook into the template section grows? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
