id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform
1884,don't cache .parrot_current_git_describe,coke,,"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.)",bug,new,normal,2.11,configure,2.10.0,medium,,,dukeleto,,,
