= Announce: RubyGems Release 1.1.0

Release 1.1.0 adds some new features and fixes some bugs.

New features:

* RubyGems now uses persistent connections on index updates. Index
updates are
much faster now.
* RubyGems only updates from a latest index by default, cutting
candidate gems
for updates to roughly 1/4 (at present). Index updates are even
faster
still.
* `gem list -r` may only show the latest version of a gem, add --
all to see
all gems.
* `gem spec` now extracts specifications from .gem files.
* `gem query --installed` to aid automation of checking for gems.

Bugs Fixed:

* RubyGems works with both Config and RbConfig now.
* Executables are now cleaned upon uninstall.
* You can now uninstall from a particular directory.
* Updating from non-default sources fixed.
* Executable stubs now use ruby install name in shebang.
* `gem unpack` checks every directory in Gem.path now.
* `gem install` now exits with non-zero exit code when appropriate.
* `gem update` only updates gems that need updates.
* `gem update` doesn't force remote-only updates.
* `gem update` handles dependencies properly when updating.
* Gems are now loaded in Gem.path order.
* Gem stub scripts on windows now work outside Gem.bindir.
* `gem sources -r` now works without network access.

Other Changes Include:

* RubyGems now requires Ruby > 1.8.3.
* Release notes are now printed upon installation.
* `gem env path` now prints a usable path.
* `gem install` reverts to local-only installation upon network error.
* Tar handling code refactoring and cleanup.
* Gem:ependencyInstaller's API has changed.

For a full list of changes to RubyGems, see the ChangeLog file.

== How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may
want to
install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all
you need to do is:

$ gem update --system (you might need to be admin/root)

(Note: You may have to run the command twice if you have any previosly
installed rubygems-update gems).

If you have an older version of RubyGems installed, then you can still
do it in two steps:

$ gem install rubygems-update (again, might need to be admin/root)
$ update_rubygems (... here too)

If you don't have any gems install, there is still the pre-gem
approach to getting software ... doing it manually:

1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

== To File Bugs

The RubyGems bug tracker can be found on RubyForge at:
http://rubyforge.org/tracker/?func=a...d=126&atid=575

When filing a bug, `gem env` output will be ful in diagnosing the
issue.

If you find a bug where RubyGems crashes, please provide debug output.
You can
do that with `gem --debug the_command`.

== Thanks

Keep those gems coming!

-- Jim & Chad & Eric (for the RubyGems team)

On Mar 29, 2008, at 01:41 , Eric Hodel wrote:
> = Announce: RubyGems Release 1.1.0
>
> Release 1.1.0 adds some new features and fixes some bugs.
>
> New features:
>
> * RubyGems now uses persistent connections on index updates. Index
> updates are
> much faster now.
> * RubyGems only updates from a latest index by default, cutting
> candidate gems
> for updates to roughly 1/4 (at present). Index updates are even
> faster
> still.

Double YAY!!!

On 29 Mar 2008, at 09:02, Ryan Davis wrote:
>
> On Mar 29, 2008, at 01:41 , Eric Hodel wrote:
>> = Announce: RubyGems Release 1.1.0
>>
>> Release 1.1.0 adds some new features and fixes some bugs.
>>
>> New features:
>>
>> * RubyGems now uses persistent connections on index updates. Index
>> updates are
>> much faster now.
>> * RubyGems only updates from a latest index by default, cutting
>> candidate gems
>> for updates to roughly 1/4 (at present). Index updates are even
>> faster
>> still.
>
> Double YAY!!!

Double second that, well done and thanks to the rubygems team!

On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
>
> * RubyGems now requires Ruby > 1.8.3.
> * Release notes are now printed upon installation.

Where do these release notes come from?

T.

On Sat, Mar 29, 2008 at 6:34 AM, Trans <transfire@gmail.com> wrote:
>
> On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
> >
> > * RubyGems now requires Ruby > 1.8.3.
> > * Release notes are now printed upon installation.
>
> Where do these release notes come from?


Well, from the error message I get when installing, they are supposed
to be installed in doc/release_notes/rel_1_1_0.rdoc, for some reason
I'm not getting anything in that directory buy a css stylesheet and a
makedoc.rb script.

On Mar 29, 11:26 am, "Christopher Dicely" <cmdic...@gmail.com> wrote:
> On Sat, Mar 29, 2008 at 6:34 AM, Trans <transf...@gmail.com> wrote:
>
> > On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
>
> > > * RubyGems now requires Ruby > 1.8.3.
> > > * Release notes are now printed upon installation.
>
> > Where do these release notes come from?
>
> Well, from the error message I get when installing, they are supposed
> to be installed in doc/release_notes/rel_1_1_0.rdoc, for some reason
> I'm not getting anything in that directory buy a css stylesheet and a
> makedoc.rb script.

Why would you be "getting" anything at all in that directory?

T.

On Mar 29, 10:34 am, Trans <transf...@gmail.com> wrote:
> On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
>
>
>
> > * RubyGems now requires Ruby > 1.8.3.
> > * Release notes are now printed upon installation.
>
> Where do these release notes come from?
>

The release notes came from here:

http://rubygems.rubyforge.org/svn/tr...rel_1_1_0.rdoc

That is a compact version of that ChangeLog states.

HTH,
--
Luis Lavena

On Sat, Mar 29, 2008 at 05:41:34PM +0900, Eric Hodel wrote:
> = Announce: RubyGems Release 1.1.0
>
> Release 1.1.0 adds some new features and fixes some bugs.
>
> New features:
>
> * RubyGems now uses persistent connections on index updates. Index updates
> are
> much faster now.
> * RubyGems only updates from a latest index by default, cutting candidate
> gems
> for updates to roughly 1/4 (at present). Index updates are even faster
> still.

Yay! Thank you!

--
Aaron Patterson
http://tenderlovemaking.com/

On Mar 29, 12:25 pm, Luis Lavena <luislav...@gmail.com> wrote:
> On Mar 29, 10:34 am, Trans <transf...@gmail.com> wrote:
>
> > On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
>
> > > * RubyGems now requires Ruby > 1.8.3.
> > > * Release notes are now printed upon installation.
>
> > Where do these release notes come from?
>
> The release notes came from here:
>
> http://rubygems.rubyforge.org/svn/tr...rel_1_1_0.rdoc
>
> That is a compact version of that ChangeLog states.

Okay, I guess I'm confused. Does "Release notes are now printed upon
installation" mean upon installation of RubyGems itself, or upon
installation of any gem? I was taking it to mean the later.

T.

On Mar 29, 2008, at 06:34 AM, Trans wrote:
>
> On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
>> * RubyGems now requires Ruby > 1.8.3.
>> * Release notes are now printed upon installation.
>
> Where do these release notes come from?

Dang, I didn't double-check to make sure release notes got shipped.
You will have to wait until the next release of RubyGems.

Eric Hodel <drbrain@segment7.net> wrote:

> = Announce: RubyGems Release 1.1.0
>
> If you have a recent version of RubyGems (0.8.5 or later), then all
> you need to do is:
>
> $ gem update --system (you might need to be admin/root)
>
> (Note: You may have to run the command twice if you have any previosly
> installed rubygems-update gems).

Could someone explain how to do this on Mac OS X 10.5.2? I tried:

gem --version
=> 1.0.1

sudo gem update --system

Lots of stuff scrolled by, but afterwards, I still see:

gem --version
=> 1.0.1

This might be related to the fact that

which gem
=> /usr/bin/gem

but the update process reports that gem was installed in
/System/Library/Frameworks/Ruby.framework etc etc etc.

Clearly I am just thrashing about here... Thx for any - m.


--
matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/
Leopard - http://www.takecontrolbooks.com/leop...stomizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com

On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
> Could someone explain how to do this on Mac OS X 10.5.2? I tried:
>
> gem --version
> => 1.0.1
>
> sudo gem update --system
>
> Lots of stuff scrolled by, but afterwards, I still see:
>
> gem --version
> => 1.0.1
>
> This might be related to the fact that
>
> which gem
> => /usr/bin/gem
>
> but the update process reports that gem was installed in
> /System/Library/Frameworks/Ruby.framework etc etc etc.
>
> Clearly I am just thrashing about here... Thx for any - m.

I emailed Chad about this: the gem update is installing the gem
command into

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
bin/gem

It should go into

System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem

which is the symlink from /usr/bin/gem



Dave

Dave Thomas <dave@pragprog.com> wrote:

> On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
> > Could someone explain how to do this on Mac OS X 10.5.2? I tried:
> >
> > gem --version
> > => 1.0.1
> >
> > sudo gem update --system
> >
> > Lots of stuff scrolled by, but afterwards, I still see:
> >
> > gem --version
> > => 1.0.1
> >
> > This might be related to the fact that
> >
> > which gem
> > => /usr/bin/gem
> >
> > but the update process reports that gem was installed in
> > /System/Library/Frameworks/Ruby.framework etc etc etc.
> >
> > Clearly I am just thrashing about here... Thx for any - m.
>
> I emailed Chad about this: the gem update is installing the gem
> command into
>
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> bin/gem
>
> It should go into
>
> System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem
>
> which is the symlink from /usr/bin/gem

Great info - what should I do? Repoint the symlink? Move the binary?
Either is easy...

Thx - m.

--
matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/
Leopard - http://www.takecontrolbooks.com/leop...stomizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com

On Mar 29, 2008, at 15:22 PM, Dave Thomas wrote:
> On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
>> Could someone explain how to do this on Mac OS X 10.5.2? I tried:
>>
>> gem --version
>> => 1.0.1
>>
>> sudo gem update --system
>>
>> Lots of stuff scrolled by, but afterwards, I still see:
>>
>> gem --version
>> => 1.0.1
>>
>> This might be related to the fact that
>>
>> which gem
>> => /usr/bin/gem
>>
>> but the update process reports that gem was installed in
>> /System/Library/Frameworks/Ruby.framework etc etc etc.
>>
>> Clearly I am just thrashing about here... Thx for any - m.
>
> I emailed Chad about this: the gem update is installing the gem
> command into
>
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> bin/gem
>
> It should go into
>
> System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem
>
> which is the symlink from /usr/bin/gem

Hrm, this is odd. I had a working RubyGems 1.1.0 on apple ruby when I
released, but after removing it to restore the apple RubyGems 1.0.1, I
am again stuck with 1.0.1 like you. Perhaps I did some other monkey-
business that caused it to work correctly.

I have an idea of what the problem is, but until I figure out exactly
what the issue is, running:

sudo update_rubygems

installs RubyGems correctly.

Eric Hodel <drbrain@segment7.net> wrote:

> On Mar 29, 2008, at 15:22 PM, Dave Thomas wrote:
> > On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
> >> Could someone explain how to do this on Mac OS X 10.5.2? I tried:
> >>
> >> gem --version
> >> => 1.0.1
> >>
> >> sudo gem update --system
> >>
> >> Lots of stuff scrolled by, but afterwards, I still see:
> >>
> >> gem --version
> >> => 1.0.1
> >>
> >> This might be related to the fact that
> >>
> >> which gem
> >> => /usr/bin/gem
> >>
> >> but the update process reports that gem was installed in
> >> /System/Library/Frameworks/Ruby.framework etc etc etc.
> >>
> >> Clearly I am just thrashing about here... Thx for any - m.
> >
> I have an idea of what the problem is, but until I figure out exactly
> what the issue is, running:
>
> sudo update_rubygems
>
> installs RubyGems correctly.

Excellent - so it does! Thanks - m.

--
matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/
Leopard - http://www.takecontrolbooks.com/leop...stomizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com

On Mar 30, 12:01 am, Eric Hodel <drbr...@segment7.net> wrote:
> On Mar 29, 2008, at 15:22 PM, Dave Thomas wrote:
>
>
>
> > On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
> >> Could someone explain how to do this on Mac OS X 10.5.2? I tried:
>
> >> gem --version
> >> => 1.0.1
>
> >> sudo gem update --system
>
> >> Lots of stuff scrolled by, but afterwards, I still see:
>
> >> gem --version
> >> => 1.0.1
>
> >> This might be related to the fact that
>
> >> which gem
> >> => /usr/bin/gem
>
> >> but the update process reports that gem was installed in
> >> /System/Library/Frameworks/Ruby.framework etc etc etc.
>
> >> Clearly I am just thrashing about here... Thx for any - m.
>
> > I emailed Chad about this: the gem update is installing the gem
> > command into
>
> > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> > bin/gem
>
> > It should go into
>
> > System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem
>
> > which is the symlink from /usr/bin/gem
>
> Hrm, this is odd. I had a working RubyGems 1.1.0 on apple ruby when I
> released, but after removing it to restore the apple RubyGems 1.0.1, I
> am again stuck with 1.0.1 like you. Perhaps I did some other monkey-
> business that caused it to work correctly.
>
> I have an idea of what the problem is, but until I figure out exactly
> what the issue is, running:
>
> sudo update_rubygems
>
> installs RubyGems correctly.

And then... someone says "Windows is broken" :-P

Nevermind, just kidding ;-)

Regards,
--
Luis Lavena

Luis Lavena <luislavena@gmail.com> wrote:

> > Hrm, this is odd. I had a working RubyGems 1.1.0 on apple ruby when I
> > released, but after removing it to restore the apple RubyGems 1.0.1, I
> > am again stuck with 1.0.1 like you. Perhaps I did some other monkey-
> > business that caused it to work correctly.
> >
> > I have an idea of what the problem is, but until I figure out exactly
> > what the issue is, running:
> >
> > sudo update_rubygems
> >
> > installs RubyGems correctly.
>
> And then... someone says "Windows is broken" :-P
>
> Nevermind, just kidding ;-)

That the built-in installation of Ruby on Mac OS X 10.5 (Leopard) is
structured in a peculiar way is a well-established fact. Nothing to do
with the system; it's the use of highly non-standard paths and
permissions for Ruby (including initial installation in a framework, in
a region to which the user has no write access, so e.g. outdated gems
can't be cleaned up - and what will happen when the user is ready to
update Ruby itself is completely unclear). But we've been up and down
this road before; nothing new to see here. m.

--
matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/
Leopard - http://www.takecontrolbooks.com/leop...stomizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com

Hi,

On 3/29/08, Eric Hodel <drbrain@segment7.net> wrote:
> = Announce: RubyGems Release 1.1.0
>
> Release 1.1.0 adds some new features and fixes some bugs.

Eric, You marked this bug I reported as closed:

http://rubyforge.org/tracker/?func=d...3&group_id=126

and yet, today when I did:

sudo gem update --system

I got:

gem --version

0.9.5

I found that executable got installed in:

/usr/local/lib/ruby/site_ruby/bin

and when I try to execute 'gem' binary from that location, I get:

/gem:14: undefined method `ruby_version' for Gem:Module (NoMethodError)

And ideas?

On Mar 31, 2008, at 14:58 PM, hemant wrote:
> On 3/29/08, Eric Hodel <drbrain@segment7.net> wrote:
>> = Announce: RubyGems Release 1.1.0
>>
>> Release 1.1.0 adds some new features and fixes some bugs.
>
> Eric, You marked this bug I reported as closed:
>
> http://rubyforge.org/tracker/?func=d...3&group_id=126
>
> and yet, today when I did:
>
> sudo gem update --system
>
> I got:
>
> gem --version
>
> 0.9.5
>
> I found that executable got installed in:
>
> /usr/local/lib/ruby/site_ruby/bin
>
> and when I try to execute 'gem' binary from that location, I get:
>
> ./gem:14: undefined method `ruby_version' for Gem:Module
> (NoMethodError)
>
> And ideas?

I think this is related to the apple install problem referenced
previously in this thread. I've reopened it.

On 30 Mar 2008, at 04:01, Eric Hodel wrote:

> I have an idea of what the problem is, but until I figure out
> exactly what the issue is, running:
>
> sudo update_rubygems
>
> installs RubyGems correctly.


Am I right in assuming that the current incorrect install only creates
the following two directories which can be safely deleted once 1.1.0
is installed correctly (in /Library/Ruby) with the above command?

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/lib
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/bin

On Apr 1, 2008, at 10:51 AM, Paul Mucur wrote:
> On 30 Mar 2008, at 04:01, Eric Hodel wrote:
>> I have an idea of what the problem is, but until I figure out
>> exactly what the issue is, running:
>>
>> sudo update_rubygems
>>
>> installs RubyGems correctly.
>
> Am I right in assuming that the current incorrect install only
> creates the following two directories which can be safely deleted
> once 1.1.0 is installed correctly (in /Library/Ruby) with the above
> command?
>
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> lib
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> bin

Correct.

On Sat, Mar 29, 2008 at 8:52 AM, Trans <transfire@gmail.com> wrote:
>
>
> On Mar 29, 11:26 am, "Christopher Dicely" <cmdic...@gmail.com> wrote:
>
>
> > On Sat, Mar 29, 2008 at 6:34 AM, Trans <transf...@gmail.com> wrote:
> >
> > > On Mar 29, 4:41 am, Eric Hodel <drbr...@segment7.net> wrote:
> >
> > > > * RubyGems now requires Ruby > 1.8.3.
> > > > * Release notes are now printed upon installation.
> >
> > > Where do these release notes come from?
> >
> > Well, from the error message I get when installing, they are supposed
> > to be installed in doc/release_notes/rel_1_1_0.rdoc, for some reason
> > I'm not getting anything in that directory buy a css stylesheet and a
> > makedoc.rb script.
>
> Why would you be "getting" anything at all in that directory?

Well, the upgrade is giving an error message after it installs the new
version saying it can't find the release notes there. Since the upgrade
creates the directory, you would think it would populate it if it is
going to look for release notes to display there and produce an error
message if they are missing.