From: Michael Wood <michael.g.wood@intel.com>
To: toaster@yoctoproject.org
Subject: Re: [PATCH 1/1] toaster: show packages that were setscened into existence too
Date: Thu, 10 Mar 2016 16:26:58 +0000 [thread overview]
Message-ID: <56E1A052.3010705@intel.com> (raw)
In-Reply-To: <d9d10e78db78f03dffee5a995695a75ebc901e20.1457415518.git.brian.avery@intel.com>
Thanks sent with some commit messages fixes to openembedded-core
http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118796.html
and pushed to toaster-next
On 08/03/16 05:50, brian avery wrote:
> We were previously ignoring pkgs that came in from a setscene (like
> from an sstate mirror). With this patch we can use pkgs than come
> from sstate for image customisation as well.
> [YOCTO #9137]
>
> Signed-off-by: brian avery <brian.avery@intel.com>
> ---
> meta/classes/toaster.bbclass | 25 +++++++++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/toaster.bbclass b/meta/classes/toaster.bbclass
> index 51a4c74..4afaf1c 100644
> --- a/meta/classes/toaster.bbclass
> +++ b/meta/classes/toaster.bbclass
> @@ -112,6 +112,26 @@ def _toaster_load_pkgdatafile(dirpath, filepath):
> pass # ignore lines without valid key: value pairs
> return pkgdata
>
> +python toaster_package_dumpdata_setscene() {
> + """
> + Dumps the data created by package_setscene
> + """
> + # replicate variables from the package.bbclass
> + packages = d.getVar('PACKAGES', True)
> + pkgdatadir = d.getVar('PKGDATA_DIR', True)
> + # scan and send data for each package
> + lpkgdata = {}
> + for pkg in packages.split():
> + try:
> + lpkgdata = _toaster_load_pkgdatafile(pkgdatadir + "/runtime/", pkg)
> + except:
> + # these are typically foo-locale which actually point into foo-locale-<language> in runtime-rprovides
> + bb.note("toaster_package_dumpdata_setscene: failed to load pkg information for: %s:%s"%(pkg,sys.exc_info()[0]))
> + # Fire an event containing the pkg data
> + bb.event.fire(bb.event.MetadataEvent("SinglePackageInfo", lpkgdata), d)
> +
> +}
> +
>
> python toaster_package_dumpdata() {
> """
> @@ -120,8 +140,6 @@ python toaster_package_dumpdata() {
> # replicate variables from the package.bbclass
>
> packages = d.getVar('PACKAGES', True)
> - pkgdest = d.getVar('PKGDEST', True)
> -
> pkgdatadir = d.getVar('PKGDESTWORK', True)
>
> # scan and send data for each package
> @@ -362,6 +380,9 @@ toaster_collect_task_stats[eventmask] = "bb.event.BuildCompleted bb.build.TaskSu
> addhandler toaster_buildhistory_dump
> toaster_buildhistory_dump[eventmask] = "bb.event.BuildCompleted"
>
> +do_packagedata_setscene[postfuncs] += "toaster_package_dumpdata_setscene "
> +do_packagedata_setscene[vardepsexclude] += "toaster_package_dumpdata_setscene "
> +
> do_package[postfuncs] += "toaster_package_dumpdata "
> do_package[vardepsexclude] += "toaster_package_dumpdata "
>
next prev parent reply other threads:[~2016-03-10 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 5:50 [PATCH 0/1] toaster: Y9137 get packages from sstate brian avery
2016-03-08 5:50 ` [PATCH 1/1] toaster: show packages that were setscened into existence too brian avery
2016-03-10 16:26 ` Michael Wood [this message]
2016-03-08 15:07 ` [PATCH 0/1] toaster: Y9137 get packages from sstate Barros Pena, Belen
2016-03-08 15:10 ` Brian Avery
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=56E1A052.3010705@intel.com \
--to=michael.g.wood@intel.com \
--cc=toaster@yoctoproject.org \
/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.