On Fri, 2019-08-02 at 07:37 +0000, [email protected] wrote: > Hi, > > On Thu, Aug 01, 2019 at 04:51:38PM +0000, chris.laplante--- via > Openembedded-core wrote: > <snip> > > I'm interesting in adding SRC_URI support to buildhistory (or a > > similar mechanism), and would like to get some input. > > Yes to this. > > Also would be nice if there was an easy way to add bitbake variables > to buildhistory. > > I've patched our tree so that SRC_URI, LICENSE and CVE_PRODUCT are > archived in buildhistory. SRC_URI has many uses and changes and > patches can be easily identified. Same with LICENSE, any changes > trigger a review. CVE_PRODUCT is exported so that we can do QA check > to make sure mapping from CVE_PRODUCT for non CLOSED licenses exists > to NVD database product names (maintaining a white list of recipes > which don't have any CVEs yet).
I think this supports my point about being more interested in patches allowing people to extend/customise buildhistory than just adding X. Whilst we want to have good defaults, there are always going to be niche cases for people wanting to extend it... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
