[Rubygems-developers] dependency version constraints

Chad Woolley thewoolleyman at gmail.com
Fri Jul 13 19:14:10 EDT 2007


On 7/13/07, TRANS <transfire at gmail.com> wrote:
> On 7/13/07, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> >
> > On Jul 13, 2007, at 11:13 , TRANS wrote:
> >
> > > I have a question about versioning and the gem command...
> > >
> > > If use #gem to constrain the version, does the gems dependencies
> > > likewise become constrained? Eg. If I have gem 'foo-1.0' that depends
> > > on a gem 'bar 2.0+', does
> > >
> > >   gem 'foo', '>= 1.0'
> > >
> > > automatically cause:
> > >
> > >   gem 'foo', '>= 2.0'
> >
> > Huh?
> >
> > Why would a dependency from foo-1.0 to bar-2.0+ change a gem call on
> > foo for 1+ to 2+?
>
> Oops. that's a type. The last line should read:
>
>    gem 'bar', '>= 2.0'
>

I think the answer is yes.  Whatever gem spec end up getting loaded,
that spec is used to determine what it's dependency versions are.


More information about the Rubygems-developers mailing list