[Rubygems-developers] What is right and wrong with dependencies definitions?

Austin Ziegler halostatue at gmail.com
Wed Nov 7 08:03:03 EST 2007

On 11/6/07, Luis Lavena <luislavena at gmail.com> wrote:
> On 11/7/07, Austin Ziegler <halostatue at gmail.com> wrote:
> > On 11/6/07, Luis Lavena <luislavena at gmail.com> wrote:
> > > Been updating some gems locally (crafted by myself) and found a
> > > curious situation:
> > > Eric told me on #ruby-lang that Hoe include itself as dependency since
> > > it's needed to perform gem 'check' operations.
> > This and the other issues would be solved if someone added a
> > "development dependencies" list (or a "gem dependencies", as in
> > dependencies for working with the gem itself, not with the package
> > contained within the gem... sort of).
> In "The Real World"(tm) users read the documentation from the source
> package to fulfill the required dependencies to compile build and pack
> the application/library.

Yeah. It'd just be nice if we could say:

  gem install --for-development foobar


Mostly, the problem is the same as everything else... someone needs to
take the time to make a patch ;)

Austin Ziegler * halostatue at gmail.com * http://www.halostatue.ca/
               * austin at halostatue.ca * http://www.halostatue.ca/feed/
               * austin at zieglers.ca

More information about the Rubygems-developers mailing list