From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: openembedded-core@lists.openembedded.org
Cc: Anders Wallin <anders.wallin@windriver.com>,
Saul Wold <saul.wold@windriver.com>,
Anders Wallin <wallinux@gmail.com>,
Paul Eggleton <bluelightning@bluelightning.org>
Subject: Re: [OE-core][PATCH v2] scripts/contrib/image-manifest: add new script
Date: Fri, 16 Apr 2021 09:15:21 +1200 [thread overview]
Message-ID: <1729190.8hzESeGDPO@linc> (raw)
In-Reply-To: <1676223428C19209.13795@lists.openembedded.org>
On Friday, 16 April 2021 08:31:58 NZST Paul Eggleton wrote:
> Hi folks
>
> On Friday, 9 April 2021 06:03:36 NZST Anders Wallin wrote:
> > image-manifest: script to generate product/image specific BOM
> >
> > The image-manifest script generates image specific reports based on
> > an image manifest file. Currently there is data generated by buildhistory,
> > pkgdata, and license manifest but this data is poorly formated and spread
> > across multiple text files. This script can generate a single JSON output
> > file that is machine readable by other tools.
> >
> > The manifest-info collects package information and stores the information
> > in a tarball. manifest-info can be configured using a json configuration
> > file. The default configuration including all possible options can be
> > dumped using the dump-config subcommand.
> >
> > image-manifest takes an image manifest file as input to get the runtime
> > dependencies. As an option image-manifest can also use the build
> > dependency
> > file, pn-buildlist, to get the build dependencies excluding native
> > packages.
> >
> > This script extends the oe-image-manifest script [0] done by Paul Eggleton
> >
> > [0]
> > https://github.com/intel/clear-linux-dissector-web/blob/master/layerindex/
> > st atic/files/oe-image-manifest
>
> So I've thought some more about this. At minimum I think this script should
> be under contrib/
Hmm, as Richard points out, it *is* already under contrib - I think I got that
mixed up with another script I'd looked at separately. Still, my other
comments stand.
Paul
prev parent reply other threads:[~2021-04-15 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 18:03 [OE-core][PATCH v2] scripts/contrib/image-manifest: add new script Anders Wallin
2021-04-15 20:31 ` Paul Eggleton
2021-04-15 22:00 ` Saul Wold
[not found] ` <1676223428C19209.13795@lists.openembedded.org>
2021-04-15 21:15 ` Paul Eggleton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1729190.8hzESeGDPO@linc \
--to=bluelightning@bluelightning.org \
--cc=anders.wallin@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@windriver.com \
--cc=wallinux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.