Rake Hates Me Today

Ruby
1

I’m trying to package up a new gem to release, but Rake and I just
can’t seem to get along today. In my Rakefile I have:

Rake::GemPackageTask.new(spec) do |pkg|
pkg.need_zip = true
pkg.need_tar = true
end

When I try to run that it does build the gem, but then complains with:

…
rake aborted!
no such option: noop

Commenting out the need_… calls removes the issue, but I really do
need the archives too.

Any tips?

Thanks.

James Edward G. II

2

On Tuesday 15 November 2005 03:42 pm, James Edward G. II wrote:

…
rake aborted!
no such option: noop

This is caused by a changed in the FileUtils package the Rake uses.
There is
a beta version of Rake available that doesn’t have that problem. You
can get
the beta with:

gem install rake --source http://onestepback.org/betagems

3

On Nov 15, 2005, at 3:07 PM, Jim W. wrote:

This is caused by a changed in the FileUtils package the Rake
uses. There is
a beta version of Rake available that doesn’t have that problem.
You can get
the beta with:

gem install rake --source http://onestepback.org/betagems

Worked perfectly. Thank you Jim!

James Edward G. II

4

On Wed, 16 Nov 2005, Jim W. wrote:

This is caused by a changed in the FileUtils package the Rake uses. There is
a beta version of Rake available that doesn’t have that problem. You can get
the beta with:

What’s the change that broke it? I suggested a change recently but
tried to ensure it was backwards compatible (a change to recursive
copy to allow the skipping of failures). This was post 1.8.3.

gem install rake --source http://onestepback.org/betagems

    Hugh
5

On Tuesday 15 November 2005 07:43 pm, Hugh S. wrote:

What’s the change that broke it? I suggested a change recently but
tried to ensure it was backwards compatible (a change to recursive
copy to allow the skipping of failures). This was post 1.8.3.

The FileUtils.cd command no long accepts a :noop option.