Confusing RubyGems...

[Luke Bayes]

Hey Folks,

I just had a really good chat yesterday with Carlos about a particular RubyGem and thought it would be good to spread the word a little more widely.

If you see a RubyGem named:

   sprout-[somename]-library

   sprout-[somename]-bundle

Unfortunately, these only work with the legacy Sprout release (0.7.x).

Also, I haven't updated them in quite some time.

One of the big features of the latest Sprouts (1.x.x), is that it doesn't require all this separation and creation of multiple, diverse RubyGems. It just wants regular old Ruby code, but if we use Gems to package and distribute that code, that's fine.

If you'd like to consume something that exists in a legacy library, you can download that SWC or src directly, and manually add it to your library_path.

For example:

1) download Foo.swc and save into ./lib/Foo.swc

2) Edit your build task like:

    mxmlc 'Mine.swf' do |t|

       t.library_path << 'lib/Foo.swc'

       # other configuration like 'input'

    end

Eazy, right?

Thanks!

Luke