On Feb 22, 2009, at 05:03, Tom Cloyd wrote:

> "Directory doc already exists, but it looks like it
> isn't an RDoc directory. Because RDoc doesn't want to risk
> destroying any of your existing files, you'll need to
> specify a different output directory name (using the
> --op <dir> option)."
>
> It can't recognize it's own output? I've never seen rdoc act like  
> this before.

RDoc doesn't write out the file tagging the directory it generated  
until the end, this is probably a bug.

> OK. Start over. Fake another update. Delete the /doc file. Result:
>
> "No newer files."

I've only gotten this to reproduce when I have a doc dir.