12971 2018-10-25 14:18:24 +0000 expose poky package metadata 2026-08-13 15:24:27 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.7 x86 Multiple NEW Low enhancement Future 1 pokylinux unassigned infras.ab.watcher Infras.watcher konrad.scherer michael.opdenacker pidge pokylinux raj.khem randy.macleod ross.burton tim.orling --- --- Don't know oldest_to_newest 81957 0 pokylinux 2018-10-25 14:18:24 +0000 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. 81960 1 mhalstead 2018-10-25 15:01:57 +0000 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. 91759 2 richard.purdie 2021-10-14 15:15:12 +0000 We could do this by adding packagedata output into the layer index in some way. 106527 3 randy.macleod 2026-08-13 15:24:27 +0000 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.