hemant
8/9/2008 11:06:00 AM
On Sat, Aug 9, 2008 at 3:27 PM, Ryan Davis <ryand-ruby@zenspider.com> wrote=
:
>
> On Aug 8, 2008, at 21:57 , Pe=F1a, Botp wrote:
>
>> For the benefit of us nubies, maybe rdoc should also update hoe if it
>> finds it at lower version (cause otherwise it should not install since i=
t
>> would not run anyway). just a suggestion.
>
> huh?
>
> rdoc shouldn't update hoe or any other gem. Rubygems should...
>
> What I don't understand is how you installed a newer rdoc that requires a
> newer hoe, but somehow didn't update hoe. Either something messed up with
> your install and dependencies weren't updated (usually they're first tho)
> or... I have no idea.
>
> Actually... this is odd:
>
> dependencies:
> - !ruby/object:Gem::Dependency
> name: hoe
> type: :development
> version_requirement:
> version_requirements: !ruby/object:Gem::Requirement
> requirements:
> - - ">=3D"
> - !ruby/object:Gem::Version
> version: 1.7.0
> version:
>
> hoe is a developer dependency, so it shouldn't be activated when you use =
the
> rdoc cmdline tool. I think you might have a mix of rdoc versions?
Well well, thats not my experience at all, very strangely, gems that
have hoe as build dependency end up requiring hoe, when I try to
require the gem. In many cases, i had to edit the gemspec, to remove
hoe as dependency.