From: Jeremy McAnally <jeremymcanally@...>
Date: 2008-02-04T00:12:45+09:00
Subject: Re: Why gem built with hoe depends on hoe?

I use newgem, which sits on top of hoe (and removes it from the
deplist).  It's written by Dr. Nic and works really, really well.

I haven't tried Mr Bones.  Perhaps I will on my next project...

--Jeremy

On Feb 3, 2008 9:49 AM, pluskid <pluskid@gmail.com> wrote:
> On Feb 2, 10:51 pm, Tim Pease <tim.pe...@gmail.com> wrote:
>
> > On Feb 1, 2008 6:20 AM, pluskid <plus...@gmail.com> wrote:
> >
> > > Hi,
> >
> > > I find hoe a cool tool to build and release gems. But I find that
> > > the gem built with hoe get a dependency to hoe automatically.
> > > I think the user will only need to install hoe if he want to build
> > > the gem manually. So adding this dependency automatically
> > > is unreasonable, isn't it?
> >
> > > Or am I wrong? Is it that the gem built by hoe need hoe to run?
> > > Thanks!
> >
> > You should look at Mr Bones. It does the same thing as hoe, but
> > without the viral dependency.
> >
> > sudo gem install bones
> >
> > <http://codeforpeople.rubyforge.org/bones>
> >
> > Blessings,
> > TwP
> Yeah! It looks great! Even with integrate with rspec. Hmm. I'll
> investigate it more. Thanks!
>
>



-- 
http://www.jeremymcanally.com/

My books:
Ruby in Practice
http://www.manning.com/mcanally/

My free Ruby e-book
http://www.humblelittlerubybook.com/

My blogs:
http://www.mrneighborly.com/
http://www.rubyinpractice.com/