From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Pascal Bach <pascal.bach@siemens.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Passing additional data from packages to be used during image creation
Date: Sat, 21 Jan 2017 11:44:32 +0000 [thread overview]
Message-ID: <1484999072.9391.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <1484817397-7308-1-git-send-email-pascal.bach@siemens.com>
On Thu, 2017-01-19 at 10:16 +0100, Pascal Bach wrote:
> I would like to pass some additional data generated during the
> creation of a package to the image creation step.
> The idea is to use this data to generate a more detailed manifest of
> what is included in the image. In the concrete case
> I would like to pass a list of required copyright files that need to
> be checked for during image creation.
>
> My current approach is to add this list as a new variable COPYRIGHTS
> to the pkgdata of each package.
> Using the image manifest to determine the package this allows me to
> compile a list of all required copyrights.
>
> The following patch allows to add extra variables to pkgdata and thus
> allows to pass additional data
>
> - [PATCH] package.bbclass: allow additional variables to be added to
>
> Is this a valid approach or did a miss a simpler way to access any
> package data during image creation?
I'm curious if adding something to PACKAGEVARS would work or if not,
why not?
Cheers,
Richard
next prev parent reply other threads:[~2017-01-21 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 9:16 Passing additional data from packages to be used during image creation Pascal Bach
2017-01-19 9:16 ` [PATCH] package.bbclass: allow additional variables to be added to pkgdata Pascal Bach
2017-01-21 11:44 ` Richard Purdie [this message]
2017-01-24 9:12 ` Passing additional data from packages to be used during image creation Pascal Bach
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=1484999072.9391.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pascal.bach@siemens.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.