On Wed, Sep 17, 2014 at 1:16 PM, Richard Purdie <[email protected]> wrote: > On Wed, 2014-09-17 at 16:08 +0800, Hongxu Jia wrote: >> The idea of incremental sig is: >> >> New sig file = Old sig file (if available) + New sig items in current build. >> >> Limit the modification within the dump_lockedsigs, and add two variables >> 'self.lockedsigs_types' and 'self.lockedsigs_raw' keep old sig file. >> >> How to config for incremental dump: >> ... >> USER_CLASSES += "sstate_lockedsig" >> SIGGEN_LOCKEDSIGS_CONFIG = "${TOPDIR}/locked-sigs.inc" >> require ${SIGGEN_LOCKEDSIGS_CONFIG} >> ... >> >> Signed-off-by: Hongxu Jia <[email protected]> > > I'm fine with the idea in principle. Why can't we do something like: ... > which is substantially simpler though?
Wouldn't it keep accumulating locked hashes for same recipes? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
