I have been working on a release-notes bbclass which will for each recipe included in am image extract stuff like package name, license info, cve info, SUMMARY, DESCRIPTION etc. and generate LaTex files. repo diffmanifests is used to extract the difference between a previous manifest and the current manifest. Each patch committed has a JIRA ticket number, and a LaTex file is generated with a symbolic link to our JIRA server. Everything is collected by a separate project, and once the LaTex files are complete, I only have to do make <product>-release-notes.pdf.
Once it is merged locally, I am considering upstreaming. Best Regards, Ulf Samuelsson > 11 juni 2018 kl. 15:46 skrev Michael Habibi <mikehab...@gmail.com>: > > Our use case is to capture the license files, manifest (package/version), and > download information only for packages we modify/add. We use our own layer to > modify/add packages, everything coming from standard Yocto layers are > untouched. > > Is there a way to generate this information on a layer-by-layer basis, > instead of a full manifest that includes all standard, unmodified packages? > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
