Allow .cache directory to be configurable?

[bebraw]

It looks like gh-pages figures out .cache dir like this:

function getCacheDir() {
  return path.relative(process.cwd(), path.resolve(__dirname, '../.cache'));
}

This can get rather nasty in case you are using gh-pages in a cli wrapper. What if we introduced cachePath option that, if set, would override this function? This would give me the flexibility I need.

[regular]

Isn't the clone option doing what you are looking for?

[bebraw]

@regular That's actually close! I realized there's a little issue, though. copy(files, basePath, options.clone); will fail if clone directory is within basePath. You would need to do something more clever than that for this to work. As it is, it will yield just ENOENT, mkdir ''.

[regular]

@bebraw I got that too (also have the clone directory inside the basePath). I was able to resolve this by using relative paths rather than absolute paths. There seems to be a bug in utils.js that only surfaces when paths are absolute.

[bebraw]

@regular Ah, I see. Thanks for the tip!