[Rubygems-developers] require_path inconsistency
rich at infoether.com
Thu Dec 18 07:50:02 EST 2003
On Dec 18, 2003, at 7:19 AM, Chad Fowler wrote:
> While I was just firing up my gem_server and trying to get some docs
> installed for browsing on one of the modules, I ran across some
> behavior I
> didn't like. But, I wanted to get some opinions before changing it.
> Right now, it's possible in the gem spec to have a require_path which
> doesn't exist in the gem. So, for example, I could install a gem that
> nothing but a subdirectory named "chad" but set my require_path to
> Given the way RubyGems is supposed to operate, I would think that this
> behavior would *never* be desirable. So, I think we should check at
> generation time to ensure that the require_path actually exists in the
Agreed...at generation time. A gem should not be generated with faulty
information in it (so far as we can tell). This includes the
in addition to the 'require_path'.
> But, I just woke up. :)
> What do you all think?
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
More information about the Rubygems-developers