Development
Edit
News
RubyGems 1.3.5
Posted 4 months ago by Eric Hodel
rubygems-update version 1.3.5 has been released!
* <http://rubygems.rubyforge.org/>
* <http://rubyforge.org/projects/rubygems>
* <http://rubygems.org/>
RubyGems is a package management framework for
... [More]
Ruby.
This gem is an update for the RubyGems software. You must have an
installation of RubyGems before this update can be applied.
See Gem for information on RubyGems (or `ri Gem`)
To upgrade to the latest RubyGems, run:
$ gem update --system # you might need to be an administrator or root
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to use the following instructions
if you see "Nothing to update".
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 RubyGems 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
For more details and other options, see:
ruby setup.rb --help
Changes:
### 1.3.5 / 2009-07-21
Bug fixes:
* Fix use of prerelease gems.
* Gem.bin_path no longer escapes path with spaces. Bug #25935 and #26458.
Deprecation Notices:
* Bulk index update is no longer supported (the code currently remains, but not
the tests)
* Gem::manage_gems was removed in 1.3.3.
* Time::today was removed in 1.3.3. [Less]
RubyGems 1.3.4
Posted 6 months ago by Eric Hodel
= Announce: RubyGems Release 1.3.4
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.4 fixes some bugs and adds some features.
Bug Fixes:
* Fixed various warnings
* Gem::ruby_version works correctly for 1.8 branch and trunk
* Prerelease gems now show up in `gem list` and can be used
* Fixed option name for `gem setup --format-executable`
* RubyGems now matches Ruby > 1.9.1 gem paths
* Gem::RemoteFetcher#download now works for explicit Windows paths across
drives. Bug #25882 by Lars Christensen
* Fix typo in Gem::Requirement#parse. Bug #26000 by Mike Gunderloy.
Deprecation Notices:
* Bulk index update is no longer supported (the code currently remains, but not
the tests)
* Gem::manage_gems was removed in 1.3.3.
* Time::today was removed in 1.3.3.
For a full list of changes to RubyGems and the contributor for each change, 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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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!
-- The RubyGems team [Less]
RubyGems 1.3.3
Posted 7 months ago by Eric Hodel
= Announce: RubyGems Release 1.3.3
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.3 fixes some bugs and adds some features.
New Features:
* `gem server` allows port names (from /etc/services) with --port.
* `gem server` now has search that jumps to RDoc. Patch #22959 by Vladimir
Dobriakov.
* `gem spec` can retrieve single fields from a spec (like `gem spec rake
authors`).
* Gem::Specification#has_rdoc= is deprecated and ignored (defaults to true)
* RDoc is now generated regardless of Gem::Specification#has_rdoc?
Bug Fixes:
* `gem clean` now cleans up --user-install gems. Bug #25516 by Brett
Eisenberg.
* Gem.bin_path now escapes paths with spaces.
* Rake extension builder uses explicit correctly loads rubygems when invoking
rake.
* Prerelease versions now match "~>" correctly. Patch #25759 by Yossef
Mendelssohn.
* Check bindir for executables, not root when validating. Bug reported by
David Chelimsky.
* Remove Time.today, no way to override it before RubyGems loads. Bug #25564
by Emanuele Vicentini
* Raise Gem::Exception for #installation_path when not installed. Bug #25741
by Daniel Berger.
* Don't raise in Gem::Specification#validate when homepage is nil. Bug #25677
by Mike Burrows.
* Uninstall executables from the correct directory. Bug #25555 by Brett
Eisenberg.
* Raise Gem::LoadError if Kernel#gem fails due to previously-loaded gem. Bug
reported by Alf Mikula.
Deprecation Notices:
* Gem::manage_gems has been removed.
* Time::today has been removed early. There was no way to make it warn and be
easy to override with user code.
For a full list of changes to RubyGems and the contributor for each change, 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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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!
-- The RubyGems team [Less]
RubyGems 1.3.2
Posted 7 months ago by Eric Hodel
= Announce: RubyGems Release 1.3.2
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.2 fixes some bugs and adds some features.
Select New Features:
* RubyGems now loads plugins from rubygems_plugin.rb in installed gems.
This can be used to add commands (See Gem::CommandManager) or add
install/uninstall hooks (See Gem::Installer and Gem::Uninstaller).
* Gem::Version now understands prerelease versions using letters. (eg.
'1.2.1.b') Thanks to Josh Susser, Alex Vollmer and Phil Hagelberg.
* RubyGems now includes a Rake task for creating gems which replaces rake's
Rake::GemPackageTask. See Gem::PackageTask.
* Gem::find_files now returns paths in $LOAD_PATH.
* Added Gem::promote_load_path for use with Gem::find_files
* Added Gem::bin_path to make finding executables easier. Patch #24114 by
James Tucker.
* Various improvements to build arguments for installing gems.
* `gem contents` added --all and --no-prefix.
* Gem::Specification
* #validate strips directories and errors on not-files.
* #description no longer removes newlines.
* #name must be a String.
* FIXME and TODO are no longer allowed in various fields.
* Added support for a license attribute. Feature #11041 (partial).
* Removed Gem::Specification::list, too much process growth. Bug #23668 by
Steve Purcell.
* `gem generate_index`
* Can now generate an RSS feed.
* Modern indicies can now be updated incrementally.
* Legacy indicies can be updated separately from modern.
Select Bugs Fixed:
* Better gem activation error message. Patch #23082.
* Kernel methods are now private. Patch #20801 by James M. Lawrence.
* Fixed various usability issues with `gem check`.
* `gem update` now rescues InstallError and continues. Bug #19268 by Gabriel
Wilkins.
* Allow 'https', 'file' as a valid schemes for --source. Patch #22485.
* `gem install`
* Now removes existing path before installing. Bug #22837.
* Uses Gem::bin_path in executable stubs to work around Kernel#load bug in
1.9.
* Correctly handle build args (after --) via the API. Bug #23210.
* --user-install
* `gem install --no-user-install` now works. Patch #23573 by Alf Mikula.
* `gem uninstall` can now uninstall from ~/.gem. Bug #23760 by Roger Pack.
* setup.rb
* Clarify RubyGems RDoc installation location. Bug #22656 by Gian Marco
Gherardi.
* Allow setup to run from read-only location. Patch #21862 by Luis Herrera.
* Fixed overwriting ruby executable when BASERUBY was not set. Bug #24958
by Michael Soulier.
* Ensure we're in a RubyGems dir when installing.
* Deal with extraneous quotation mark when autogenerating .bat file on MS
Windows. Bug #22712.
Deprecation Notices:
* Gem::manage_gems has been removed.
* Time::today will be removed in RubyGems 1.4.
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 and Daniel Berger 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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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!
-- The RubyGems team [Less]
RubyGems 1.3.1
Posted about 1 year ago by Eric Hodel
= Announce: RubyGems Release 1.3.1
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.1 fixes some bugs.
Bugs fixed:
* Disregard ownership of ~ under Windows while creating ~/.gem. Fixes
issues related to no uid support under Windows.
* Fix requires for Gem::inflate, Gem::deflate, etc.
* Make Gem.dir respect :gemhome value from config. (Note: this feature may be
removed since it is hard to implement on 1.9.)
* Kernel methods are now private. Patch #20801 by James M. Lawrence.
* Gem::location_of_caller now behaves on Windows. Patch by Daniel Berger.
* Silence PATH warning.
Deprecation Notices:
* Gem::manage_gems will be removed on or after March 2009.
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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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) [Less]
RubyGems 1.3.1
Posted about 1 year ago by Eric Hodel
= Announce: RubyGems Release 1.3.1
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.1 fixes some bugs.
Bugs fixed:
* Disregard ownership of ~ under Windows while creating ~/.gem. Fixes
issues related to no uid support under Windows.
* Fix requires for Gem::inflate, Gem::deflate, etc.
* Make Gem.dir respect :gemhome value from config. (Note: this feature may be
removed since it is hard to implement on 1.9.)
* Kernel methods are now private. Patch #20801 by Stefan Rusterholz.
* Gem::location_of_caller now behaves on Windows. Patch by Daniel Berger.
* Silence PATH warning.
Deprecation Notices:
* Gem::manage_gems will be removed on or after March 2009.
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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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) [Less]
RubyGems 1.3.1
Posted about 1 year ago by Eric Hodel
= Announce: RubyGems Release 1.3.0
NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to
... [More]
update".
Release 1.3.0 fixes some bugs.
Bugs fixed:
* Disregard ownership of ~ under Windows while creating ~/.gem. Fixes
issues related to no uid support under Windows.
* Fix requires for Gem::inflate, Gem::deflate, etc.
* Make Gem.dir respect :gemhome value from config. (Note: this feature may be
removed since it is hard to implement on 1.9.)
* Kernel methods are now private. Patch #20801 by Stefan Rusterholz.
* Gem::location_of_caller now behaves on Windows. Patch by Daniel Berger.
* Silence PATH warning.
Deprecation Notices:
* Gem::manage_gems will be removed on or after March 2009.
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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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) [Less]
RubyGems 1.3.0
Posted about 1 year ago by Eric Hodel
= Announce: RubyGems Release 1.3.0
Release 1.3.0 adds new features and fixes some bugs.
Note! Some versions of RubyGems have a bug that will prevent automatic updates. If RubyGems says it has nothing to update, run:
$ gem
... [More]
install rubygems-update
$ update_rubygems
New features:
* RubyGems doesn't print LOCAL/REMOTE titles for `gem query` and friends if
stdout is not a TTY, except with --both.
* Added Gem.find_files, allows a gem to discover features provided by other
gems.
* Added pre/post (un)install hooks for packagers of RubyGems. (Not for gems
themselves).
* RubyGems now installs gems into ~/.gem if GEM_HOME is not writable. Use
--no-user-install command-line switch to disable this behavior.
* Fetching specs for update now uses If-Modified-Since requests.
* RubyGems now updates the ri cache when the rdoc gem is installed and
documentation is generated.
Deprecation Notices:
* Gem::manage_gems now warns when called. It will be removed on or after March
2009.
Bugs Fixed:
* RubyGems 1.3.0+ now updates when no previous rubygems-update is installed.
Bug #20775 by Hemant Kumar.
* RubyGems now uses the regexp we already have for `gem list --installed`. Bug
#20876 by Nick Hoffman.
* Platform is now forced to Gem::Platform::RUBY when nil or blank in the
indexer. Fixes various uninstallable gems.
* Handle EINVAL on seek. Based on patch in bug #20791 by Neil Wilson.
* Fix HTTPS support. Patch #21072 by Alex Arnell.
* RubyGems now loads all cache files even if latest has been loaded. Bug
#20776 by Uwe Kubosch.
* RubyGems checks for support of development dependencies for #to_ruby. Bug
#20778 by Evan Weaver.
* Now specifications from the future can be loaded.
* Binary script uninstallation fixed. Bug #21234 by Neil Wilson.
* Uninstallation with -i fixed. Bug #20812 by John Clayton.
* Gem::Uninstaller#remove_all now calls Gem::Uninstaller#uninstall_gem so hooks
get called. Bug #21242 by Neil Wilson.
* Gem.ruby now properly escaped on windows. Fixes problem with extension
compilation.
* `gem lock --strict` works again. Patch #21814 by Sven Engelhardt.
* Platform detection for Solaris was improved. Patch #21911 by Bob Remeika.
Other Changes Include:
* `gem help install` now describes _version_ argument to executable stubs
* `gem help environment` describes environment variables and ~/.gemrc and
/etc/gemrc
* On-disk gemspecs are now read in UTF-8 and written with a UTF-8 magic comment
* Rakefile
* If the SETUP_OPTIONS environment variable is set, pass its contents as
arguments to setup.rb
* lib/rubygems/platform.rb
* Remove deprecated constant warnings and really deprecate them. (WIN32,
etc).
* lib/rubygems/remote_fetcher.rb
* Now uses ~/.gem/cache if the cache dir in GEM_HOME is not writable.
* lib/rubygems/source_index.rb
* Deprecate options to 'search' other than Gem::Dependency instances and
issue warning until November 2008.
* setup.rb
* --destdir folder structure now built using Pathname, so it works for
Windows platforms.
* test/*
* Fixes to run tests when under test/rubygems/. Patch by Yusuke ENDOH
[ruby-core:17353].
* test/test_ext_configure_builder.rb
* Locale-free patch by Yusuke Endoh [ruby-core:17444].
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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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) [Less]
RubyGems 1.3.0
Posted about 1 year ago by Eric Hodel
= Announce: RubyGems Release 1.3.0
Release 1.3.0 adds new features and fixes some bugs.
Note! Some versions of RubyGems have a bug that will prevent automatic updates. If RubyGems says it has nothing to update, run:
$ gem
... [More]
install rubygems-update
$ update_rubygems
New features:
* RubyGems doesn't print LOCAL/REMOTE titles for `gem query` and friends if
stdout is not a TTY, except with --both.
* Added Gem.find_files, allows a gem to discover features provided by other
gems.
* Added pre/post (un)install hooks for packagers of RubyGems. (Not for gems
themselves).
* RubyGems now installs gems into ~/.gem if GEM_HOME is not writable. Use
--no-user-install command-line switch to disable this behavior.
* Fetching specs for update now uses If-Modified-Since requests.
* RubyGems now updates the ri cache when the rdoc gem is installed and
documentation is generated.
Deprecation Notices:
* Gem::manage_gems now warns when called. It will be removed on or after March
2009.
Bugs Fixed:
* RubyGems 1.3.0 now updates when no previous rubygems-update is installed.
Bug #20775 by Hemant Kumar.
* RubyGems now uses the regexp we already have for `gem list --installed`. Bug
#20876 by Nick Hoffman.
* Platform is now forced to Gem::Platform::RUBY when nil or blank in the
indexer. Fixes various uninstallable gems.
* Handle EINVAL on seek. Based on patch in bug #20791 by Neil Wilson.
* Fix HTTPS support. Patch #21072 by Alex Arnell.
* RubyGems now loads all cache files even if latest has been loaded. Bug
#20776 by Uwe Kubosch.
* RubyGems checks for support of development dependencies for #to_ruby. Bug
#20778 by Evan Weaver.
* Now specifications from the future can be loaded.
* Binary script uninstallation fixed. Bug #21234 by Neil Wilson.
* Uninstallation with -i fixed. Bug #20812 by John Clayton.
* Gem::Uninstaller#remove_all now calls Gem::Uninstaller#uninstall_gem so hooks
get called. Bug #21242 by Neil Wilson.
* Gem.ruby now properly escaped on windows. Fixes problem with extension
compilation.
* `gem lock --strict` works again. Patch #21814 by Sven Engelhardt.
* Platform detection for Solaris was improved. Patch #21911 by Bob Remeika.
Other Changes Include:
* `gem help install` now describes _version_ argument to executable stubs
* `gem help environment` describes environment variables and ~/.gemrc and
/etc/gemrc
* On-disk gemspecs are now read in UTF-8 and written with a UTF-8 magic comment
* Rakefile
* If the SETUP_OPTIONS environment variable is set, pass its contents as
arguments to setup.rb
* lib/rubygems/platform.rb
* Remove deprecated constant warnings and really deprecate them. (WIN32,
etc).
* lib/rubygems/remote_fetcher.rb
* Now uses ~/.gem/cache if the cache dir in GEM_HOME is not writable.
* lib/rubygems/source_index.rb
* Deprecate options to 'search' other than Gem::Dependency instances and
issue warning until November 2008.
* setup.rb
* --destdir folder structure now built using Pathname, so it works for
Windows platforms.
* test/*
* Fixes to run tests when under test/rubygems/. Patch by Yusuke ENDOH
[ruby-core:17353].
* test/test_ext_configure_builder.rb
* Locale-free patch by Yusuke Endoh [ruby-core:17444].
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: RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed. You will need to follow the second set of update
instructions if you see "Nothing to update".
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) [Less]
RubyGems 1.2.0
Posted about 1 year ago by Eric Hodel
= 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
... [More]
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) [Less]
Recent Posts
-
The ohloh people google map
by
Tomas Jesson
Unfortunally, OpenStreetMap for this time is less detailed than GMap. -
Research: Effects of Gender Socialization on Females in Open Source
by
Tomas Jesson
Interesting topic, isn't sex affect Open Source? :) -
Kudos counter not updated?
by
davide_alberani
Wooops - it makes sense. :-) I thought it was (at least partially) related to the involvement (e...
Recent Reviews
-
Joomla!
by
Tomas Jesson
I have been using Joomla for a while now and absolutely love it. It is missing one critical eleme... -
nviron
by
rolandha
The whole thing is in development and there is no stable release currently! Please be patient ... -
Jedi Code Library
by
dilshan
JEDI JCL is my ultimate choice for Delphi projects and it contain functions to handle system oper...
Copyright © 2009 Geeknet, Inc., All Rights Reserved.