Hey Bryan, just tried to run the wizard again on a sample and overwrote the files. Essentially it didn't seem to really have any significant changes except in the routes. After that it griped about still needing pre31 installed. After wiping out the Gemfile.lock it fired up, but it has some other screwball things going on.
Could you give a quick incantation of what you'd normally do in an upgrade situation as an example? It seems that hobo upgrades can really create some headaches if you don't have a firm grasp on everything. Would REALLY appreciate it. Kindest regards, -yll On May 17, 9:49 am, Bryan Larsen <[email protected]> wrote: > On Tue, May 17, 2011 at 9:27 AM, ylluminate <[email protected]> wrote: > > Also, quick question, on the upgrades, is there a hobo evocation that > > needs to be run in order to update an existing project's source? So > > let's say we get to an update that makes a significant change (not > > that pre31 -> rc makes a real diff), is something like `hobo upgrade` > > that will diff things out for the developer to show what needs to be > > updated code wise in the new update to the project files? > > You can rerun the setup_wizard generator (or any other generator), and > it gives you a chance to see the diff for all changes. > > What I usually do is press "y" for most or all files and use git tools > to look over the diffs and put my changes back in. > > Bryan -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
