From: "nikolai.weibull@..." <nikolai.weibull@...>
Date: 2009-10-22T01:55:06+09:00
Subject: Re: Config.datadir in 1.9.1

On Oct 21, 4:38 pm, "nikolai.weib...@gmail.com"
<nikolai.weib...@gmail.com> wrote:

> In 1.8.6., Config.datadir('package') would give you the gem-relative
> data directory for a gem.  In 1.9.1, Config doesn’t seem to even be
> loaded at startup.  What happened?  What am I supposed to use instead?
>  Even if you get Config loaded it still won’t work, as the gem’s paths
> are already added to $LOAD_PATH, so Rubygems won’t load the
> specification and thus Gem.datadir('package') will give a nil result.
>
> Is this a bug or am I doing something wrong?

OK, this is definitely due to a deficiency in Rubygems on 1.9.*:

http://rubyforge.org/tracker/index.php?func=detail&aid=22617&group_id=126&atid=575

What amazes me is that this has gone unfixed for nearly a year.  I
don’t think that it’s a trivial problem, but I’m amazed that everyone
has gotten by without this for such a long time.  Am I the only one
using Config.datadir?