# \--disable-gems permanent?

**URL:** <https://www.ruby-forum.com/t/disable-gems-permanent/185773>\
**Category:** Ruby\
**Created:** [March 25, 2010, 10:53pm UTC](https://www.ruby-forum.com/t/disable-gems-permanent/185773 "2010-03-25T22:53:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [March 25, 2010, 10:53pm UTC](https://www.ruby-forum.com/t/disable-gems-permanent/185773/1 "2010-03-25T22:53:07Z")

</div>

Before I report a bug report to core on this one, thought I’d see if  
anybody had some feedback first.

Currently with 1.9.1, if you run  
$ ruby --disable-gems test.rb

where

test.rb is:  
require ‘rubygems’  
require ‘gem\_name’

I get:

C:\installs\ruby191p376\lib\ruby\gems\1.9.1\gems\redcar-0.3.3\>ruby -v  
–disable-gems test.rb  
ruby 1.9.2dev (2010-03-24) [i386-mingw32]  
Warning:C:/installs/ruby\_trunk\_installed/lib/ruby/site\_ruby/1.9.1/rubygems/config\_file.rb:34:  
Win32API is deprecated after Ruby 1.9.1; use dl directly instead  
test.rb:2:in `require': no such file to load -- win32/api (LoadError) from test.rb:2:in`’

and am forced to instead fo

require ‘rubygems’  
gem ‘gem\_name’  
require ‘gem\_name’

I assume this is unexpected to others, as well?  
Thanks.  
-rp