On Mon, 1 Feb 2010, John Trupiano wrote:
> >
> > On Mon, Feb 1, 2010 at 1:31 PM, Hugh Sasse <[email protected]> wrote:
> >
> >>
> Hugh,
>
> I put the library up on GitHub: http://github.com/jtrupiano/gem_filer
Thank you, I've had a look at this, and it looks like it will be useful.
>
> Essentially you'll just want to use the bin/gemfiler script to run whatever
> code you want to interrogate. If you're trying to get a list of the gems
> your test environment activates when it's loaded, you should be able to run
> this from the root of your rails project:
>
>
> RAILS_ENV=test path/to/bin/gemfiler --rails
I'm not using rails, but there's a rake option there, so that should be
OK....
>
> Note that this command will not actually run your tests, all it does is load
> the test environment. So if you lazily require any of your test or app
> dependencies (which is very possible), those may not get picked up.
Yes, I saw the comment about threads in there, and I don't think that is
a concern for me yet.
>
> Check out the README for various examples on how to use gem_filer. Note
> that this library is very early stage and it's quite possible that I'll
> never actually release it as a gem. However, seeing as you seemed to be
> asking for some functionality that I believe it provides, I thought I'd
> share it with you.
>
> Also, take the opportunity to look under the covers. You'll find that
> RubyGems itself provides me with gem activation data that I use to create
> the Gemfile (via Gem.loaded_specs).
Yes, I noticed some of that going on. Thank you.
>
> -John
Hugh
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
