rubygems-update 1.3.4 → 1.3.5

data/doc/release_notes/rel_0_9_5.rdoc

@@ -1,108 +0,0 @@
-= Announce: RubyGems Release 0.9.5
-
-Release 0.9.5 adds several new features and fixes several bugs.
-
-Major New Features Include:
-
-* Platform support
-* Automatic installation of platform gems
-* New bandwidth and memory friendlier index file format
-* "Offline" mode (--no-update-sources)
-* Bulk update threshold can be specified (-B, --bulk-threshold)
-* New `gem fetch` command
-* `gem` now has "really verbose" output when you specify -v
-* Improved stubs and `gem.bat` on mswin, including better compatiblity
-  with the One-Click Installer.
-
-Other Changes Include:
-
-* Time::today is deprecated and will be removed at a future date
-* Gem::manage_gems is deprecated and will be removed at a future date
-* `gem install --include-dependencies` (-y) is now deprecated since it is the
-  default, use --ignore-dependencies to turn off automatic dependency
-  installation
-* Multi-version diamond dependencies only are installed once
-* Processing a YAML bulk index update takes less memory
-* `gem install -i` makes sure all depenencies are installed
-* `gem update --system` reinstalls into the prefix it was originally installed
-  in
-* `gem update --system` respects --no-rdoc and --no-ri flags
-* HTTP basic authentication support for proxies
-* Gem::Specification#platforms should no longer be a String, use
-  Gem::Platform::CURRENT when building binary gems instead
-* `gem env` has more diagnostic information
-* require 'rubygems' loads less code
-* sources.gem is gone, RubyGems now uses built-in defaults
-* `gem install --source` will no longer add --source by default, use `gem
-  sources --add` to make it a permanent extra source
-* `gem query` (list) no longer prints details by default
-* Exact gem names are matched in various places
-* mkrf extensions are now supported
-* A gem can depend on a specific RubyGems version
-* `gem_server` is now `gem server`
-* `gemlock` is now `gem lock`
-* `gem_mirror` is now `gem mirror`
-* `gemwhich` is now `gem which`
-* `gemri` is no longer included with RubyGems
-* `index_gem_repository.rb` is now `gem generate_index`
-* `gem` performs more validation of parameters
-* Custom rdoc styles are now supported
-* Gem indexer no longer removes quick index during index creation
-* Kernel#require only rescues a LoadError for the file being required now
-* `gem dependencies` can now display some information for remote gems
-* Updating RubyGems now works with RUBYOPT=-rubygems
-
-Special thanks to:
-
-* Daniel Berger
-* Luis Lavena
-* Tom Copeland
-* Wilson Bilkovich
-
-The full set of changes including contributors is included in the ChangeLog.
-
-== What is RubyGems?
-
-RubyGems is a package management system for Ruby applications and
-libraries.  RubyGems one command download makes installing Ruby
-software fun and enjoyable again. (Ok, not really.)
-
-Many gems are available for download from the RubyForge site.  Browse
-the list of gems with a "gem list --remote" command and download what
-you need with a simple "gem install <name-of-gem>".  RubyGems takes
-care of the details of installing, not only the gem you requested, but
-also any gems needed by the software you selected.
-
-== How can I get RubyGems?
-
-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)
-
-== What's Next
-
-Integration into Ruby 1.9, RubyGems 1.0.
-
-== Thanks
-
-Keep those gems coming!
-
--- Jim & Chad & Eric (for the RubyGems team)
-

data/doc/release_notes/rel_1_0_0.rdoc

@@ -1,67 +0,0 @@
-= Announce: RubyGems Release 1.0.0
-
-Release 1.0.0 fixes several bugs.
-
-Major New Features Include:
-
-* RubyGems warns about various problems with gemspecs during gem building
-* More-consistent versioning for the RubyGems software
-
-Other Changes Include:
-
-* Fixed various bugs and problems with installing gems on Windows
-* Fixed using `gem server` for installing gems
-* Various operations are even more verbose with --verbose
-* Built gems are now backwards compatible with 0.9.4
-* Improved detection of RUBYOPT loading rubygems
-* `ruby setup.rb` now has a --help option
-* Gem::Specification#bindir is now respected on installation
-* Executable stubs can now be installed to match ruby's name, so if ruby is
-  installed as 'ruby18', foo_exec will be installed as 'foo_exec18'
-* `gem unpack` can now unpack into a specific directory with --target
-* OpenSSL is no longer required by default
-
-Deprecations and Deletions:
-
-* Kernel#require_gem has been removed
-* Executables without a shebang will not be wrapped in a future version, this
-  may cause such executables to fail to operate on installation
-* Gem::Platform constants other than RUBY and CURRENT have been removed
-* Gem::RemoteInstaller was removed
-* Gem::Specification#test_suite_file and #test_suite_file= are deprecated in
-  favor of #test_file and #test_file=
-* Gem::Specification#autorequire= has been deprecated
-* Time::today will be removed in a future version
-
-== How can I get RubyGems?
-
-NOTE:  If you have installed RubyGems using a package 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)
-
-== Thanks
-
-Keep those gems coming!
-
--- Jim & Chad & Eric (for the RubyGems team)
-

data/doc/release_notes/rel_1_0_1.rdoc

@@ -1,56 +0,0 @@
-= Announce: RubyGems Release 1.0.1
-
-Release 1.0.1 fixes a few bugs.
-
-Bugs Fixed:
-
-* Installation on Ruby 1.8.3 through 1.8.5 fixed
-* `gem build` on 1.8.3 fixed
-
-Other Changes Include:
-
-* Since RubyGems 0.9.5, RubyGems is no longer supported on Ruby 1.8.2 or older,
-  this is official in RubyGems 1.0.1.
-
-== How can I get RubyGems?
-
-NOTE:  If you have installed RubyGems using a package 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=add&group_id=126&atid=575
-
-When filing a bug, `gem env` output will be helpful 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)
-

data/doc/release_notes/rel_1_1_0.rdoc

@@ -1,85 +0,0 @@
-= 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::DependencyInstaller'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=add&group_id=126&atid=575
-
-When filing a bug, `gem env` output will be helpful 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)
-

data/doc/release_notes/rel_1_1_1.rdoc

@@ -1,64 +0,0 @@
-= Announce: RubyGems Release 1.1.1
-
-Release 1.1.1 fixes some bugs.
-
-Bugs Fixed:
-
-* Gem.prefix now returns non-nil only when RubyGems was installed outside
-  sitelibdir or libdir.
-* The `gem server` gem list now correctly links to gem details.
-* `gem update --system` now passes --no-format-executable to setup.rb.
-* Gem::SourceIndex#refresh! now works with multiple gem repositories.
-* Downloaded gems now go into --install-dir's cache directory.
-* Various fixes to downloading gem metadata.
-* `gem install --force` now ignores network errors too.
-* `gem pristine` now rebuilds extensions.
-* `gem update --system` now works on virgin Apple ruby.
-* Gem::RemoteFetcher handles Errno::ECONNABORTED.
-* Printing of release notes fixed.
-
-For a full list of changes to RubyGems including credits, 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=add&group_id=126&atid=575
-
-When filing a bug, `gem env` output will be helpful 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)
-

data/doc/release_notes/rel_1_2_0.rdoc

@@ -1,105 +0,0 @@
-= Announce: RubyGems Release 1.2.0
-
-Release 1.2.0 adds new features and fixes some bugs.
-
-New features:
-
-* RubyGems no longer performs bulk updates and instead only fetches the gemspec
-  files it needs.  Alternate sources will need to upgrade to RubyGems 1.2 to
-  allow RubyGems to take advantage of the new metadata updater.  If a pre 1.2
-  remote source is in the sources list, RubyGems will revert to the bulk update
-  code for compatibility.
-* RubyGems now has runtime and development dependency types.  Use
-  #add_development_dependency and #add_runtime_dependency.  All typeless
-  dependencies are considered to be runtime dependencies.
-* RubyGems will now require rubygems/defaults/operating_system.rb and
-  rubygems/defaults/#{RBX_ENGINE}.rb if they exist.  This allows packagers and
-  ruby implementers to add custom behavior to RubyGems via these files.  (If
-  the RubyGems API is insufficient, please suggest improvements via the
-  RubyGems list.)
-* /etc/gemrc (and windows equivalent) for global settings
-* setup.rb now handles --vendor and --destdir for packagers
-* `gem stale` command that lists gems by last access time
-
-Bugs Fixed:
-
-* File modes from gems are now honored, patch #19737
-* Marshal Gem::Specification objects from the future can now be loaded.
-* A trailing / is now added to remote sources when missing, bug #20134
-* Gems with legacy platforms will now be correctly uninstalled, patch #19877
-* `gem install --no-wrappers` followed by `gem install --wrappers` no longer
-  overwrites executables
-* `gem pristine` now forces reinstallation of gems, bug #20387
-* RubyGems gracefully handles ^C while loading .gemspec files from disk, bug
-  #20523
-* Paths are expanded in more places, bug #19317, bug #19896
-* Gem::DependencyInstaller resets installed gems every install, bug #19444
-* Gem.default_path is now honored if GEM_PATH is not set, patch #19502
-
-Other Changes Include:
-
-* setup.rb
-  * stub files created by RubyGems 0.7.x and older are no longer removed.  When
-    upgrading from these ancient versions, upgrade to 1.1.x first to clean up
-    stubs.
-  * RDoc is no longer required until necessary, patch #20414
-* `gem server`
-  * Now completely matches the output of `gem generate_index` and
-    has correct content types
-  * Refreshes from source directories for every hit.  The server will no longer
-    need to be restarted after installing gems.
-* `gem query --details` and friends now display author, homepage, rubyforge url
-  and installed location
-* `gem install` without -i no longer reinstalls dependencies if they are in
-  GEM_PATH but not in GEM_HOME
-* Gem::RemoteFetcher now performs persistent connections for HEAD requests,
-  bug #7973
-
-For a full list of changes to RubyGems and the contributor for each change, see
-the ChangeLog file.
-
-Special thanks to Chad Wooley for backwards compatibility testing and Luis
-Lavena for continuing windows support.
-
-== 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=add&group_id=126&atid=575
-
-When filing a bug, `gem env` output will be helpful 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)
-