The .sigdata file isn't usually used by the end user, we can generate it by default, but it would be good if we have a switch for it, for example, BB_NO_SIGDATA, this would not save much disk space (only about 120M for a core-image-sato build), but it would save a mount of disk I/O, when many people (or multi builds) works on the same sever, the disk I/O is usually the bottleneck, the build would cost much time on I/O waiting, reduce the disk I/O would save time.
The sigdata files are there to allow for debugging of the system. Whilst they may not be commonly used, they are invaluable in trying to debug what went into a given checksum and what might have changed. I seriously doubt these have much impact on overall build time. I'd want to see statistics proving this was some kind of build bottleneck before any such patch was taken. Please feel free to provide supportive evidence of this being a problem but right now I'm not convinced it is (quite the opposite) so I'm marking the bug accordingly.
As an aside, if I/O is a worry, we could compress them. Again, I'd like to see numbers showing this is a real problem first though.
(In reply to comment #2) > As an aside, if I/O is a worry, we could compress them. Again, I'd like to > see numbers showing this is a real problem first though. Hi RP, I've done several builds without the generation of .sigdata and python's temp/run.*, but it doesn't make much difference, only about 40 seconds saved for a core-image-sato build (the host's load is not high, the whole builds cost 156m53.460s), so drop this one is the right way.
Verified as per above comments.