FS#17611 - [ruby] split rubygems out of package ruby
Attached to Project:
Arch Linux
Opened by S.Knoth (cro) - Saturday, 26 December 2009, 22:09 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 January 2010, 13:01 GMT
Opened by S.Knoth (cro) - Saturday, 26 December 2009, 22:09 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 January 2010, 13:01 GMT
|
Details
Description:
Please split rubygems out of package ruby, so that it can be updated cleanly again. Updating rubygems by itself by "gem update --system" might conflict with pacman's package information of the installed package containing rubygems. With rubygems I mean the rubygems gem manager that manages the so called gems for ruby and _not_ any of the gems. An alternative approach might be to leave rubygems in package ruby but then to update the ruby package orderly when a new version of either ruby or rubygems (or of both of course) is released. That didn't work over the last months, rubygems was outdated most of the time leading to gems not working and requesting an update. And flagging the ruby package out-to-date might be confusing if not ruby but the rubygems part is outdated. As far as I know, ruby and rubygems are two seperate projects, so it is unpractical to have them together in one package. Besides, it should be defined and documented which files are managed by rubygems and which by pacman to avoid conflicts. I would call this circumstance "nested package managers". :) Additional info: http://bbs.archlinux.org/viewtopic.php?id=83254 |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 23 January 2010, 13:01 GMT
Reason for closing: Won't implement
Additional comments about closing: Upstream choice to distribute them together. Reopen if upstream situation changes.
Saturday, 23 January 2010, 13:01 GMT
Reason for closing: Won't implement
Additional comments about closing: Upstream choice to distribute them together. Reopen if upstream situation changes.
But why do those upstream people bundle an outdated version of rubygems to ruby? What's with rubygems versions from http://www.rubygems.org? They're on 1.3.5 versus 1.3.1 of the ruby source tarball. How are we supposed to update rubygems cleanly? "gem update --system" might conflict with pacman. Can somebody confirm my thinking? But I don't see how it could not since it has to change files that where installed by pacman. Problems can arise when the update process adds or removes files.
Weren't there times when rubygems wasn't part of the ruby package on Arch Linux? What was different? Wasn't there rubygems in the source distribution of ruby in those days?
Might it be possible to install an updated version from rubygems.org over the gems version from ruby-lang.org while packaging?
"gem update --system" is probably not the best idea...