Project

General

Profile

Bug #3564

'gem uninstall' doesn't remove executables which were installed with --format-executable option

Added by mrkn (Kenta Murata) over 10 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
ruby -v:
ruby 1.9.2dev (2010-07-11 revision 28613) [x86_64-darwin10.4.0]
Backport:
[ruby-core:31238]

Description

=begin
'gem uninstall' command doesn't remove executables installed with --format-executable option, but ones installed without the option.
The command, unfortunately, doesn't allow us the option so we are obliged to remove the executables manually.

Operation Log:

[12:15:24#104]mrkn$ ls /opt/rubies/bin/spec*
/opt/rubies/bin/spec /opt/rubies/bin/spec-1.9.2
[14:03:11#105]mrkn$ gem-1.9.2 uninstall --format-executable rspec
ERROR: While executing gem ... (OptionParser::InvalidOption)
invalid option: --format-executable
[14:03:47#106]mrkn$ gem-1.9.2 uninstall rspec
Remove executables:
autospec, spec

in addition to the gem? [Yn] y
Removing autospec
Removing spec

You have requested to uninstall the gem:
rspec-1.3.0
addressable-2.1.2 depends on [rspec (>= 1.0.8)]
autotest-growl-0.2.4 depends on [rspec (>= 1.3.0)]
bundler-0.9.26 depends on [rspec (>= 0)]
g-1.4.0 depends on [rspec (>= 0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] y
Successfully uninstalled rspec-1.3.0
[14:04:24#107]mrkn$ ls /opt/rubies/bin/spec*
/opt/rubies/bin/spec-1.9.2
=end

#1

Updated by raggi (James Tucker) over 10 years ago

=begin

On 13 Jul 2010, at 06:11, Kenta Murata wrote:

Bug #3564: 'gem uninstall' doesn't remove executables which were installed with --format-executable option
http://redmine.ruby-lang.org/issues/show/3564

Author: Kenta Murata
Status: Open, Priority: Normal
Category: lib, Target version: 1.9.2
ruby -v: ruby 1.9.2dev (2010-07-11 revision 28613) [x86_64-darwin10.4.0]

'gem uninstall' command doesn't remove executables installed with --format-executable option, but ones installed without the option.
The command, unfortunately, doesn't allow us the option so we are obliged to remove the executables manually.

Operation Log:

[12:15:24#104]mrkn$ ls /opt/rubies/bin/spec*
/opt/rubies/bin/spec /opt/rubies/bin/spec-1.9.2
[14:03:11#105]mrkn$ gem-1.9.2 uninstall --format-executable rspec
ERROR: While executing gem ... (OptionParser::InvalidOption)
invalid option: --format-executable
[14:03:47#106]mrkn$ gem-1.9.2 uninstall rspec
Remove executables:
autospec, spec

in addition to the gem? [Yn] y
Removing autospec
Removing spec

You have requested to uninstall the gem:
rspec-1.3.0
addressable-2.1.2 depends on [rspec (>= 1.0.8)]
autotest-growl-0.2.4 depends on [rspec (>= 1.3.0)]
bundler-0.9.26 depends on [rspec (>= 0)]
g-1.4.0 depends on [rspec (>= 0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] y
Successfully uninstalled rspec-1.3.0
[14:04:24#107]mrkn$ ls /opt/rubies/bin/spec*
/opt/rubies/bin/spec-1.9.2

This is a known issue in RubyGems, I have proposed that --format-executable be removed as a command line option from the install command, and only exist in the configuration (gemrc). This way behaviour will be consistent unless the user explicitly changes the configuration. I have not yet come around to writing either solution, or removing the option.

There is a core problem with this whereby RubyGems does not maintain a manifest of items installed, and as such it is not aware at the time of uninstall, which binary name was installed with the package. Arbitrary use of the format executable parameter to install is for now, very much not recommended.

This bug should be reported to one of the RubyGems trackers, either at:

http://help.rubygems.org

or

http://rubyforge.org/tracker/?group_id=126

Please do note though, that this is a dup of a bug already in the rubyforge tracker:

http://rubyforge.org/tracker/index.php?func=detail&aid=25826&group_id=126&atid=575

Thank you for the report. This ticket may be closed on the ruby redmine.

=end

#2

Updated by mame (Yusuke Endoh) over 10 years ago

  • Status changed from Open to Rejected

=begin
Hi,

2010/7/13 James Tucker jftucker@gmail.com:

This bug should be reported to one of the RubyGems trackers, either at:

http://help.rubygems.org

or

http://rubyforge.org/tracker/?group_id=126

Umm. I didn't realize that rubygems has a separate bug tracker.
There are quite a lot of tickets related to rubygems in this
redmine. Should they be forwarded to the tracker?
IMO, it is not friendly for casual user that they should report
an issue to different trackers, though.

Please do note though, that this is a dup of a bug already in the rubyforge tracker:

http://rubyforge.org/tracker/index.php?func=detail&aid=25826&group_id=126&atid=575

Thank you for the report. This ticket may be closed on the ruby redmine.

Done. Thanks.

--
Yusuke Endoh mame@tsg.ne.jp
=end

#3

Updated by raggi (James Tucker) over 10 years ago

=begin

On 13 Jul 2010, at 14:52, Yusuke Endoh wrote:

Issue #3564 has been updated by Yusuke Endoh.

Status changed from Open to Rejected

Hi,

2010/7/13 James Tucker jftucker@gmail.com:

This bug should be reported to one of the RubyGems trackers, either at:

http://help.rubygems.org

or

http://rubyforge.org/tracker/?group_id=126

Umm. I didn't realize that rubygems has a separate bug tracker.
There are quite a lot of tickets related to rubygems in this
redmine. Should they be forwarded to the tracker?
IMO, it is not friendly for casual user that they should report
an issue to different trackers, though.

I just got back on to ruby-core. I know Eric monitors here. I'm happy to help track reports given here too, but really this is more down to you guys, as I'm not a member of ruby-core. I will help users either way, and am happy to defer to your opinion / request.

Regards,

James

=end

Also available in: Atom PDF