Re: [Rubygems-developers] The deprecation of autorequire

2009-01-15 Thread Hugh Sasse
On Thu, 15 Jan 2009, Austin Ziegler wrote: > On Thu, Jan 15, 2009 at 12:17 AM, Chad Woolley > wrote: > Some of this might be helped if RubyGems provided a "default require" > piece of metadata that could be queried about a gem. One of the > complaints that I've heard—and don't really have a fix

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-15 Thread Austin Ziegler
On Thu, Jan 15, 2009 at 12:17 AM, Chad Woolley wrote: > On Wed, Jan 14, 2009 at 10:08 PM, Jim Weirich wrote: >> Only use a 'gem' command if you want something other than the latest >> installed version of a gem. You application should arrange to invoke the >> gem command early in the program, af

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Chad Woolley
On Wed, Jan 14, 2009 at 10:08 PM, Jim Weirich wrote: > Only use a 'gem' command if you want something other than the latest > installed version of a gem. You application should arrange to invoke the > gem command early in the program, after 'rubygems' has been required, but > before any other req

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Jim Weirich
On Jan 14, 2009, at 8:35 PM, Daniel Berger wrote: No, for that example you're correct. I just thought that, as more of the stdlib is bundled separately as a gem it may become more of a hassle to have to do 'gem' + 'require'. I thought it would still be useful for those authors, but it se

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Daniel Berger
Luis Lavena wrote: AFAIK autorequire has been deprecated. A good reason will be that under certain circumstances you don't want to load the whole library of a gem. gem 'rspec', '~> 1.1.10' # allow me to have a code locked to a specific mayor.minor safe versions require 'spec/expectations' w

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Luis Lavena
On Wed, Jan 14, 2009 at 7:17 PM, Berger, Daniel wrote: > Hi, > > I'm curious as to why Gem#gem doesn't autorequire the library: > > require 'rubygems' > gem 'ptools' > require 'ptools' # Must I do this? > p File.which('ruby') > > If I leave out the 'require' on line 3 it doesn't work. > > I checke

Re: [Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Berger, Daniel
> -Original Message- > From: rubygems-developers-boun...@rubyforge.org > [mailto:rubygems-developers-boun...@rubyforge.org] On Behalf > Of Berger, Daniel > Sent: Wednesday, January 14, 2009 2:18 PM > To: rubygems-developers@rubyforge.org > Subject: [Rubygems-develo

[Rubygems-developers] The deprecation of autorequire

2009-01-14 Thread Berger, Daniel
Hi, I'm curious as to why Gem#gem doesn't autorequire the library: require 'rubygems' gem 'ptools' require 'ptools' # Must I do this? p File.which('ruby') If I leave out the 'require' on line 3 it doesn't work. I checked rubygems.rb and the $LOAD_PATH definitely includes the path where the gems