| Summary: | expose poky package metadata | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Robert Berger <pokylinux> |
| Component: | autobuilder | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | infras.ab.watcher, Infras.watcher, konrad.scherer, michael.opdenacker, pidge, pokylinux, raj.khem, randy.macleod, ross.burton, tim.orling |
| Version: | 2.7 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Robert Berger
2018-10-25 14:18:24 UTC
I asked for some clarification and this is a request to provide an interface similar to https://packages.debian.org/search?searchon=contents&keywords=tune2fs&mode=path&suite=stable&arch=any to identify which recipe/package a file is provided by in the poky distro. Is this information is already generated by the autobuilder? If so perhaps we could expose it there per build. We could do this by adding packagedata output into the layer index in some way. To do this from the command line, use: https://git.openembedded.org/openembedded-core/tree/scripts/oe-pkgdata-util Making this visible from the layer index would require more work and that needed to be done by the YP autobuilder. We don't have time for that now but perhaps some day we will. |