So to clarify your question, basically everything we would want in the
custom manifest would be in our own layer: both bbappends and new bb
recipes. Given that, you think I could still modify it like you suggest to
get what I want?
On Wed, Jun 13, 2018 at 8:59 AM Beth Flanagan wrote:
> Ok, I gue
Ok, I guess my question there then would be is how you'd determine
where a recipe "lived". Like, if meta-foo has a bbappends for
something in core, would you include it or not in your manifest?
If so, then taking the original manifest and just doing some text
manipulation in a ROOTFS_POSTPROCESS_C
Beth,
This is for internal consumption. We want to be able to generate a full
manifest, and also one that reflects how we diverged from base Yocto
distribution.
On Mon, Jun 11, 2018 at 10:55 AM Beth Flanagan wrote:
> On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi
> wrote:
> > Our use case is
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 cur
On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi wrote:
> 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
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-lay
