Posted
26 days
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]
Posted
2 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]
Posted
3 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]
Posted
8 months
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]
Posted
8 months
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]
build_tools programming development ruby packaging
|
edit tags
