On 3/5/07, Grant Cox <[EMAIL PROTECTED]> wrote: > > > 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.
Hi Grant, Daniel's test suite is also the reason I'm looking into the new structure and your problem is the one I've feared. I wonder is it possible to move your 'app' directory into the cake directory and define everything except 'vendors' as externals? 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 :) Well, I suppose you could tag your app with the framework before you update the framework. Maybe that wouldn't make sense. hmmm...... Sonic --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
