Hi bakers, I know this has been touched on before but I would like to pay a revisit if you'll bare with me for a few minutes. With the advent of cakePHP 1.2 on the horizon people have been coming out with some nice additions to the framework which require external libraries to be added to the Global 'Vendors' directory. Since I usually only keep my 'app' directory under version control this causes me re-think my practices once again. Therefore, I was wondering if you would take a minute to share your version control strategies so we may see a show of hands and see the most common set-ups used. So, which of the following set-ups do you use:
(a) Keep your entire cake installation with your application in your own Repository and merge new changes as necessary with every new release drop. (b) Keep your entire cake installation with your application in your own Repository and use svn::externals to point the framework files to the cakePHP repository. (c) Keep only your 'app' directories under version control so that they can be checked out into any version of the framework. (d) Other. One other thing I've noticed with my set-up [(c) above] is that, while I can check out my application (written with cake 1.1.x.x) into a copy of the 1.2.x.x framework, I seem to be missing some files in my 'app' directory (and associated subdirectories) which are included in the default 1.2.x.xskeleton 'app' directory. Is there a set-up where I can automatically find the missing files using version control techniques? Cheers for your responses in advance, 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 -~----------~----~----~----~------~----~------~--~---
