[Rubygems-developers] HEADSUP RubyGems 1.2 Real Soon Now

James Tucker jftucker at gmail.com
Wed Jun 4 13:41:10 EDT 2008

On 4 Jun 2008, at 18:03, Jeremy Kemper wrote:

> On Wed, Jun 4, 2008 at 3:15 AM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> On Jun 4, 2008, at 00:33 AM, Stephen Bannasch wrote:
>>> At 6:22 PM -0700 6/3/08, Jeremy Kemper wrote:
>>>> On Tue, Jun 3, 2008 at 4:36 PM, Eric Hodel <drbrain at segment7.net>  
>>>> wrote:
>>>>> I believe RubyGems is currently feature-complete for the next  
>>>>> release.
>>>>> For
>>>>> the next while I'll be focusing on bugfixes and patches from the
>>>>> tracker.  I
>>>>> expect to release a new version in two weeks at minimum, possibly
>>>>> longer.
>>>> I'd love to see little-known --format-executable enabled by default
>>>> for gem installs.
>>> I would like the opposite to be the default.
>> I would love to make --format-executable the default, but that will  
>> cause
>> too much confusion and will inconvenience the majority too much.   
>> (Maybe I
>> shouldn't have made it default for setup.rb/gem update --system,  
>> but the two
>> new rubygems/defaults files may help improve that situation.)
> The naming changes only when that person has changed his ruby's naming
> also, so it feels natural.
> The majority have a vanilla ruby so they'll see no change or  
> confusion.

The problem is expectation. People run `ruby foo.rb` and it works, so  
they expect `gem ...` to work too. Distros pack in a link which is  
what fools people into thinking they're getting it without the suffix.

My solution to this problem is also to keep implementations seperate,  
and in that regard, continually having to add extensions to the  
commands i use daily, and really mostly messing with tab completion  
speed, is a must not. As it is, on most of our platforms I re-link gem  
to gem1(\.)?8 as appropriate.

I then switch between 'contents' with a bash function: http://pastie.textmate.org/208786

>>> -- background on my setup --
>> [...]
>>> I installed rubinius source into rubinius/code and installed it into
>>> rubinius/install.
>>> But since Rubinius doesn't have the equivalent of '-S' I need to  
>>> supply
>>> the full path to the gem.rb command.
>> `rbx gem env` will do what you want.
>> We have discussed making gem executables accessible via rbx as a  
>> subcommand,
>> `rbx rake`.  We will probably wire this in via the rubygems/ 
>> defaults file.
> jeremy
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers

More information about the Rubygems-developers mailing list