G
gabriele renzi
Hi gurus and nubys,
it seem to me that rubygems has a wrong behaviour when removing gems
with dependencies, it will remove "executables and scripts" before
asking if the user really wants to remove the library causing an unmet
dependency.
So, if, as an example, you try to remove rake but then you stop the
operation because it will create an unmet dependency, the rake script
will be lost anyway. If this is not a bug it is anyway an incorrect way
of doing things, imo.
PS
I was going to report this on the rubygems tracker but it seem to need
some maintanance, since a lot of bugs are already fixed
it seem to me that rubygems has a wrong behaviour when removing gems
with dependencies, it will remove "executables and scripts" before
asking if the user really wants to remove the library causing an unmet
dependency.
So, if, as an example, you try to remove rake but then you stop the
operation because it will create an unmet dependency, the rake script
will be lost anyway. If this is not a bug it is anyway an incorrect way
of doing things, imo.
PS
I was going to report this on the rubygems tracker but it seem to need
some maintanance, since a lot of bugs are already fixed