No, that is the wrong solution. It means that we are sweeping under the rug the fact that there is something fundamentally wrong with the gem updating process. Doing any sort of gem update process should never break the hobo system. I'm sure that gem uses its own set of "scripts" for doing all of its own processing. The problem is really contained in those privately used "scripts" for the gem system. The gem system should know about version conflicts between modules and prevent the installation of modules that it "knows" will cause such conflicts. The gem system is supposed to be "so much better than the apt-get system from what I've heard. So let's see some evidence of that...I would say. Let's really fix the problem at its source.
Sincerely, Arthur On Friday, May 2, 2014 8:55:48 AM UTC-7, Arthur Baldwin wrote: > > Hi there, > > I've been away from Hobo for a while, but was involved in prompting the > creation of InstantHobo.bash by Quillro. > I'm wondering if anyone might be interested in refining and updating > InstantHobo.bash to use the latest versions of > Ruby, Rails, and Hobo? > > Hobo 2.1 > Rails 4.x > Ruby 2.x > > and I also would like the script to prompt for the desired database: > > SQLite > MySQL > PostGreSQL > > PostGreSQL is the one I prefer, but try as I might...I always get problems > with trying to use the 'gem install pg' command. > > I very much need to start designing websites for customers using the > latest versions and PostGreSQL right away. > > Thanks for your assistance. > > Sincerely, > > Arthur Baldwin > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
