Ticket #1884 (new bug)
don't cache .parrot_current_git_describe
|Reported by:||coke||Owned by:|
Description (last modified by coke) (diff)
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:
- git pull
- configure # XXX This does not update the sha1-describe.
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.)