I'm using (b) at the moment too, but the application started as just having my app folder in version control, and the core cake libs outside of this (c). So my folder structure is more like trunk/ trunk/libs/ trunk/libs/cake_1.2.x.x_branch trunk/src/ trunk/src/config ... webroot
and to tell you the truth, this is a bit of a pain for the same reason you originally mentioned - global vendors. The only thing I use that needs this is Daniel Hofstetter's test suite, but synchronising this across our machines is already a pain, as these files are inside the externals of the cake libs, and I can't see how to actually include it in my app's repository. Right now I'm not sure what the best structure is. I like being able to update my cake libs to any revision easily, but I would like my app to automatically check out with a particular cakephp revision (the revision I was using when I committed my app) too... I guess nothing is perfect :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
