Bug 12971 - expose poky package metadata
Summary: expose poky package metadata
Status: NEW
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.7
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-10-25 14:18 UTC by Robert Berger
Modified: 2026-08-13 15:24 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Berger 2018-10-25 14:18:24 UTC
Not sure I'm posting in the right category here;)

As discussed with Khem at ELCE it might be a good idea to have some kind of exposed database where can you figure out which "file" in a package comes from which recipe.
Comment 1 Michael Halstead 2018-10-25 15:01:57 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.
Comment 2 Richard Purdie 2021-10-14 15:15:12 UTC
We could do this by adding packagedata output into the layer index in some way.
Comment 3 Randy MacLeod 2026-08-13 15:24:27 UTC
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.