Download & Extend

omega-guard requires ruby1.8 + rubygems

Project:Omega
Version:7.x-4.x-dev
Component:Documentation
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

These are my notes as a follow-up for fubhy on getting omega-guard working. Not really sure where to put it, so here it is as an issue (which probably isn't the right place, but at least it's written down). It may contain some useful tips for documentation.

After halting, and then restarting the vagrant box, I finally did get omega-guard to work. What follows are my install notes.

Question: Why does this need ruby 1.9? Guard works with ruby1.8, which is more common on Ubuntu installs. (I'm sure there's something specific that you're doing which needs 1.9, but would it be possible to downgrade it to 1.8 to save some headaches?)

vagrant@precise32:/vagrant/public/sites/all/themes/o_gemtest$ dpkg --get-selections | grep ruby
libmysql-ruby install
libruby1.9.1 install
ruby-mysql install
ruby1.9.1 install
ruby1.9.1-dev install

note1: ruby1.8 has been removed and purged from the system
note2: ruby1.9.1 contains rubygems (see below)

vagrant@precise32:/vagrant/public/sites/all/themes$ apt-cache show ruby1.9.1
Package: ruby1.9.1
Priority: optional
Section: ruby
Installed-Size: 234
Maintainer: Ubuntu Developers
Original-Maintainer: akira yamada
Architecture: i386
Version: 1.9.3.0-1ubuntu2.4
Replaces: irb1.9.1, rdoc1.9.1, rubygems1.9.1
Provides: irb1.9.1, rdoc1.9.1, ruby-interpreter, rubygems1.9.1
Depends: libruby1.9.1 (= 1.9.3.0-1ubuntu2.4), libc6 (>= 2.0)
Suggests: ruby1.9.1-examples, ri1.9.1, graphviz, ruby1.9.1-dev
Conflicts: irb1.9.1 (<< 1.9.1.378-2~), rdoc1.9.1 (<< 1.9.1.378-2~), ri (<= 4.5), ri1.9.1 (<< 1.9.2.180-3~), ruby (<= 4.5), rubygems1.9.1
(etc)

(hat tip to msonnabaum for pointing that out)

So then I went back to the steps fubhy had me working on, including:

$ cd sub_theme_generated_by_wizard
$ bundle install

Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/..
Installing addressable (2.3.2)
Installing chunky_png (1.2.7)
Installing fssm (0.2.10)
Installing sass (3.2.5)
Installing compass (0.12.2)
Installing breakpoint (1.3)
Installing coderay (1.0.8)
Installing compass-normalize (1.4.2)
Installing compass-rgbapng (0.1.1)
Installing compass-validator (3.0.1)
Installing json (1.7.6) with native extensions
Installing rdoc (3.12)
Installing css_parser (1.2.6)
Installing eventmachine (1.0.0) with native extensions
Installing http_parser.rb (0.5.3) with native extensions
Installing em-websocket (0.4.0)
Installing ffi (1.3.1) with native extensions
Installing listen (0.7.2)
Installing lumberjack (1.0.2)
Installing method_source (0.8.1)
Installing slop (3.4.3)
Installing pry (0.9.11.4)
Installing terminal-table (1.4.5)
Installing thor (0.17.0)
Installing guard (1.6.2)
Installing guard-compass (0.0.6)
Installing multi_json (1.5.0)
Installing guard-livereload (1.1.3)
Installing guard-shell (0.5.1)
Installing sassy-math (1.5)
Installing modular-scale (1.0.6)
Installing oily_png (1.0.3) with native extensions
Installing rb-fchange (0.0.6)
Installing rb-fsevent (0.9.3)
Installing rb-inotify (0.8.8)
Installing respond-to (2.6)
Installing sass-globbing (1.0.0)
Installing sassy-strings (0.3.1)
Installing singularitygs (0.0.17)
Installing susy (1.0.5)
Installing toolkit (0.2.3)
Installing yajl-ruby (1.1.0) with native extensions
Using bundler (1.2.3)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
Post-install message from rdoc:
Depending on your version of ruby, you may need to install ruby rdoc/ri data:

<= 1.8.6 : unsupported
= 1.8.7 : gem install rdoc-data; rdoc-data --install
= 1.9.1 : gem install rdoc-data; rdoc-data --install
>= 1.9.2 : nothing to do! Yay!

Note: previously it had only reported up to: Your bundle is complete!
it did not include: Use `bundle show [gemname]` to see where a bundled gem is installed. (etc)

Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
Post-install message from rdoc:
Depending on your version of ruby, you may need to install ruby rdoc/ri data:

<= 1.8.6 : unsupported
= 1.8.7 : gem install rdoc-data; rdoc-data --install
= 1.9.1 : gem install rdoc-data; rdoc-data --install
>= 1.9.2 : nothing to do! Yay!

vagrant@precise32:/vagrant/public/sites/all/themes/o_gemtest$ gem install rdoc-data; rdoc-data --install
Fetching: rdoc-data-3.12.gem (100%)
rdoc-data is only required for C ruby 1.8.7 or 1.9.1.

rdoc-data is required for JRuby.

To install ri data for RDoc 2.5+ run:

rdoc-data --install

Successfully installed rdoc-data-3.12
1 gem installed
Installing ri documentation for rdoc-data-3.12...
Installing RDoc documentation for rdoc-data-3.12…

Note: 1 gem installed
(yay!)

Finally, this works:

$ drush omega-guard o_gemtest
Compilation took 0.039s
02:55:55 - INFO - Guard::Compass is watching at your stylesheets.
02:55:55 - INFO - Guard is now watching at '/vagrant/public/sites/all/themes/o_gemtest'
02:55:55 - INFO - LiveReload 1.6 is waiting for a browser to connect.
[1] guard(main)>

Comments

#1

I'll have to investigate which of the gems requires 1.9. Not sure if we can downgrade it to 1.8. At least not if the gem is essential for us. Guard is only the underlying API, we are using multiple guard extensions and some other stuff which might very well need 1.9. I'll see what I can do!

#2

I just checked this and gave it a try with ruby1.8... It worked! :)

I did get this message after 'bundle install' too:

Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
Post-install message from rdoc:
Depending on your version of ruby, you may need to install ruby rdoc/ri data:

<= 1.8.6 : unsupported
= 1.8.7 : gem install rdoc-data; rdoc-data --install
= 1.9.1 : gem install rdoc-data; rdoc-data --install
>= 1.9.2 : nothing to do! Yay!

Not sure what failed with your setup earlier but it must've been something weird, heh.

Consequently I removed the dependency check for 1.9+ and downgraded that to a 1.8+ dependency check.

#3

#4

Title:omega-guard requires ruby1.9+» omega-guard requires ruby1.8 + rubygems

In the end it was installing bundler with gems 1.6 that had been causing problems. Upgrading to gems 1.8+ before installing the bundler fixed this.

#5

I have omega guard installed and watching scss files -- but I am getting no love from livereload?

~/d7dev/sites/default$ drush omega-guard omg4
Compilation took 0.013s
16:16:04 - INFO - Guard::Compass is watching at your stylesheets.
16:16:05 - INFO - LiveReload 1.6 is waiting for a browser to connect.
16:16:05 - INFO - Guard is now watching at '/home/joe/websites/d7dev/sites/all/themes/omg4'
overwrite css/styles.css
16:17:10 - INFO - Reloading browser: css/styles.css
overwrite css/styles.css
16:18:31 - INFO - Reloading browser: css/styles.css
[1] guard(main)>

I have an apache virtual host d7dev.dev I use to connect to the site on my local - I see the settings in the development tab on the theme settings - reading that screen it seems it should work.

But I don't see that livereload.js is being loaded -

+    // We need to add livereload.js as external script with an absolute path
+    // because otherwise Drupal core messes with the query string.
+    drupal_add_js(url($path . '/js/livereload.js', array('query' => $options, 'absolute' => TRUE)), 'external');

is this pointing to the subtheme or omega base theme? only omega has livereload.js

#6

Please open new issues for things like that. I moved your request to: #1909044: LiveReload not working

#7

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

nobody click here