bugcons - Bugs: bug #4, Support content-based signatures...

 
 

bug #4: Support content-based signatures for derived files

Submitter:  Steven Knight <knight>
Submitted:  Fri 16 Feb 2001 04:11:22 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 16 Feb 2001 04:11:22 PM UTC, original submission:  

Add a configurable mechanism for deciding if a derived file is up-to-date based on its content, not on the aggregation of its dependencies' signatures.  This helps a lot of builds by short-circuiting the build chain if an expensive rebuild of a file generated the exact same product as before.  It needs to be configurable, though, because it would be a lose for builds that put a time stamp in the derived file, in which case the contents would change every time.

 Steven Knight <knight>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follows 1 latest change.

Date Changed by Updated Field Previous Value => Replaced by
2001-02-16 knight Priority1 - Later None

Back to the top

Copyright © 2024 Free Software Foundation, Inc.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
Page source code

Powered by Savane 3.13-54b4.
Corresponding source code