On Sun, Sep 23, 2012 at 7:46 PM, S Ahmed wrote:
I see what your saying.
I guess what I am asking then is, when developing your own gem, say I am
developing my gem on my Mac in:
So this means I have to somehow modify my load_path so that I can just
require things like:
And then when I publish my gem and users use my gem, things will just work
since the gem is installed by default at a path that ruby will look in?
How then do gem developers modify their path to have this work?
They don't. They usually end up using something that 7Stud also mentioned.
Which is to say require_relative or they add a relative path to the $PATH
variable in some way.
So they don't modify their path, they use the environment that will be
given, and take advantage of this.
You can also use the file itself... you will see many different examples of
this in different gems. For example, in Rails Admin, spec/spec_helper.rb
you will see require File.expand_path('../dummy_app/config/environment',
This takes the relative location of that file and load it that way, and so
will not require it to know exactly where it was installed, but it can rely
on its own project structure.
In IRB go ahead and do that... >> File.expand_path('.') you will see what I
mean. From that piece of information, build your path as you need to
require things for your project.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.