petdance/scratch — Issue #360: don't cache .parrot_current_git_describe
Author: petdance
Created: 2011-11-01 04:25:47+00:00
State: open

When configuring parrot, the value for "git-describe" is taken from the cache file if it is present.

Here's a not-uncommon workflow that breaks in this case:

* realclean
* build
* git pull
* configure # XXX This does not update the sha1-describe.
* build

Unless there's a super compelling reason to cache this file, the value shouldn't even be stored on disk - it should go into the config hash and be calculated every time you run configure.

(similar arguments may cover other newly generated .parrot files.)