#1884: don't cache .parrot_current_git_describe
-----------------------+----------------------------------------------------
 Reporter:  coke       |       Owner:        
     Type:  bug        |      Status:  new   
 Priority:  normal     |   Milestone:  2.11  
Component:  configure  |     Version:  2.10.0
 Severity:  medium     |    Keywords:        
     Lang:             |       Patch:        
 Platform:             |  
-----------------------+----------------------------------------------------

Old description:

> 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.)

New description:

 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.)

--

Comment(by coke):

 (fix formatting in desc.)

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1884#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to