Forwarding from Charley. Looks like there's some sort of gems/hoe
interaction bug happening.
Dan
--- Begin Message ---
Well, ok. So I've figured out how to reproduce it, seems it's hoe that
actually causing an issue.
- create a basic gemspec
Gem::Specification.new do |s|
....
s.add_dependency 'user-choices' #could be any hoe generated gem
s.add_dependency 'win32-process', '>=0.5.5'
...
end
- build the gem
- install it
When it tries install the win32-api library it grabs the wrong version. Add
the dependency later and it works for this basic example, but I'm assuming
dependencies might not be ordered, since in the actual Watir gemspec, we
have a dependency on common-watir after the win32 dependency calls; common
watir is built with hoe as are some it's dependencies - user-choices and
it's required libs in our case.
It's an interesting problem, but I'm not quite sure how to solve it at this
point. Thoughts?
Charley Baker
blog: http://charleybakersblog.blogspot.com/
Lead Developer, Watir, http://wtr.rubyforge.org
QA Architect, Gap Inc Direct
On Wed, Feb 25, 2009 at 5:58 PM, Daniel Berger <djber...@gmail.com> wrote:
> Hi Charley,
>
> I don't understand why your system would do that. I just tried it on my XP
> VM:
>
> C:\>gem install win32-api
> Successfully installed win32-api-1.4.0-x86-mswin32-60
> 1 gem installed
> Installing ri documentation for win32-api-1.4.0-x86-mswin32-60...
> Installing RDoc documentation for win32-api-1.4.0-x86-mswin32-60...
>
> That's with Rubygems 1.3.1.
>
> Do you have multiple versions of Ruby installed on your system? JRuby
> maybe?
>
> Can you send me the output of "gem env"?
>
> Regards,
>
> Dan
>
> On Wed, Feb 25, 2009 at 12:18 PM, Charley Baker <charley.ba...@gmail.com>
> wrote:
> > Hi Daniel,
> >
> > I've been looking at an issue that recently popped up in the Watir
> > installation of win32-api and some sort of gem dependency issue and
> haven't
> > had any luck yet figuring this out. Since you're involved with both
> > win32-utils and rubygems, I was wondering if you might have any insight
> into
> > this. With the latest version of Rubygems 1.3.1, the feature to
> > automatically install the correct gem for the platform doesn't seem to be
> > working with Watir's chain of dependencies - it's currently installing
> the
> > 80 version of win32-api instead of the 60 version.
> >
> > If you try to install the latest version of win32-api individually it
> does
> > the right thing and the platform is resolved, the 60 version is
> installed.
> > If we try installing watir and it's dependencies on the win32 process
> > libraries, somewhere in the chain the platform gets screwed up and the 80
> > version of win32-api gets installed.
> >
> > Wondering if you have any obvious ideas or places to look, I've been
> banging
> > my head on this for the past day or two, and don't see anything
> immediately
> > apparent.
> >
> >
> > Charley Baker
> > blog: http://charleybakersblog.blogspot.com/
> > Lead Developer, Watir, http://wtr.rubyforge.org
> > QA Architect, Gap Inc Direct
> >
>
--- End Message ---
_______________________________________________
Rubygems-developers mailing list
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
