On Wed, Jun 4, 2008 at 11:46 AM, Matthieu Riou <[EMAIL PROTECTED]> wrote: > On Tue, Jun 3, 2008 at 7:43 PM, 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. >> > > Why?
Because minimizing it to just a majority vote on buildr-dev, and then packaging a Gem and uploading to RubyForge and is something we can get over and done with today. Going through the full process, not until mid/late next week. Assaf
