Eric Hodel
Eric Hodel
With this rakefile: ``` ruby task :default do sh 'echo', '; rm -rf .' end ``` when run: ``` $ rake echo ; rm -rf . ; rm -rf ....
> When you say, "not safe," do you mean merely that it won't work? It will depend on the command, some won't work, some will do wrong things. > Or...
Hi, we can’t work on examples that are sexually explicit. It’s not appropriate for users of rake looking for big fixes to be force to read such things
Rake was designed to have the behavior of `make` but be written in Ruby. Changing from timestamp to checksum could break behavior of existing rake workflows so I find it...
Rake uses glob and has for years (see @698a54980ef0e7f84447ee67f865366f56f2857a) so I think this comes from the glob changes in Ruby 2.2 since I don't see or remember rake changes to...
I need more of your Rakefile to reproduce. Except for the missing definition of a `run` method I can't see the behavior you describe: ``` $ cat t.rake desc "Run...
As a workaround, use quoting in your shell: `rake "my_task[arg1, arg2]"`
I would follow `Rake::Task`'s API, so instead of `Rake::NameSpace::get`, `Rake::NameSpace::[]` to look up a namespace: ``` ruby Rake::NameSpace['namespace_name'].clear ```
… so I'm for it. Also, there's only one method in Rake that has `get` in it, which is why I prefer `[]`.
That one is on a `Rake::Namespace` instance, the one I propose would be on the `Rake::Namespace` class. For example: ``` ruby namespace :n do task :t do puts 'work' end...