I did it the way Felix described for a while, but found I was doing a lot of work setting up the vendors for each project. Recently I created a dedicated repo for vendors and now I only need to update my vendors repo instead of working with multiple vendor directories in multiple projects.
Also in regards to the current version, you can also use Configure::version() http://api.cakephp.org/1.2/class_configure.html#a2adec719a5868c34704c367aa4d95b1 On May 8, 6:19 pm, Grant Cox <[EMAIL PROTECTED]> wrote: > Use vendor branching - then every revision of your app has the > appropriate Cake core, and you can easily handle updates / deletes to > Cake core files, even those in the app folder. > > Felix has a good screencast for using vendor > branching.http://www.debuggable.com/posts/screencast-using-vendor-branching-and... > > On May 9, 4:43 am, seb <[EMAIL PROTECTED]> wrote: > > > Mathew Nik Foscarini wrote: > > > I hope this isn't a stupid question, but how can I check what version of > > > Cake 1.2.#### is installed? > > > There's a version.txt file located in cake core files folder. > > > > I also need to update my Cake 1.2 install with the latest version. When > > > copying files over top my existing install which files should not get > > > modified? are there any I should worry about, or is it safe to write > > > overwrite everything. > > > Well, you can overwrite all cake core files. This is harmless for your app. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
