+1 on this one, for sure.
On Wed, Jun 4, 2008 at 5:43 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > Looks like we've got another dependency problem. > > There are two workarounds, install from source or remove the newer > hoe/rubyforge dependency, both of which will have to be done after > installing/upgrading 1.3.1, and every time you run gem update, which > will restore the newer dependencies. > > I'm proposing we push a new Gem to RubyForge without making an > official release, there will not be a corresponding Apache > distribution, and it will not contain any other changes from trunk > besides new version number and fixed Gem dependencies. > > Assaf >
