search

remear / jewelrybox

OS X RVM Manager
105 stars 5 forks source link

Autolibs #187

Open generalconsensus opened 11 years ago

generalconsensus commented 11 years ago

A vanilla install of Jewelry Box (and homebrew) on a Mountain Lion installation causes the following issues:

Installing requirements for osx, might require sudo password.

Skipping brew update make sure your formulas are up to date. RVM autolibs is now configured with mode '2' => 'check and stop if missing', please run rvm autolibs enable to let RVM do it's job or run and read rvm autolibs [help] or visit https://rvm.io/rvm/autolibs for more information.

Missing required packages: autoconf, automake, libtool, pkg-config, libyaml, readline, libxml2, libxslt, libksba, openssl, sqlite. RVM autolibs is now configured with mode '2' => 'check and stop if missing', please run rvm autolibs enable to let RVM do it's job or run and read rvm autolibs [help] or visit https://rvm.io/rvm/autolibs for more information.

There were package installation errors, make sure to read the log. Check Homebrew requirements https://github.com/mxcl/homebrew/wiki/Installation

To proceed rvm requires a ruby-1.9|ruby-2 compatible ruby is installed. We attempted to install ruby automatically but it failed. Please install it manually (or a compatible alternative) to proceed.

remear commented 11 years ago

RVM is giving you the opportunity to decide what you'd like to do about missing dependencies. This is the new autolibs feature of RVM.

I usually prefer to have JewelryBox not make too many rigid decisions for how the user should interact with RVM on their system. What would you like it to have done?

generalconsensus commented 11 years ago

You've made a good point, I believe that solves the issue.

remear commented 11 years ago

There's also a significant portion of the user base that doesn't like working on the command line at all. An interface is needed for managing autolibs levels and enabling/disabling it. I don't know yet how best to implement this interface in various places around the application. Suggestions are welcome.

generalconsensus commented 11 years ago

One thought is to have two buttons -- one that enables autolib ("Process with Autolib"), and one without ("Process"). Using a creative scheme you can make one button more appealing than another.