[yocto] How to archive only packages contained in a certain image

[Burton, Ross]

Those recipes are special: the gcc-source recipe fetches and and
unpacks the GCC source tree, and gcc builds it.  So gcc has no
source...  Add gcc-source explicitly to your list and you'll be
sorted.

Ross

On Mon, 4 Feb 2019 at 16:23, David Zimmermann <dzimmermann at yellowtec.com> wrote:
>
> Thanks for your helpful hints Ross !
>
> I now have a script in place which:
> - extracts package names from image manifest
> - translates package names to recipe names
> - grabs the source packages for those recipes (from what the archiver extracted according to it’s config)
>
> For two recipes, referenced by the manifest file, the archiver does extract no source packages:
> - libgcc
> - gcc-runtime
> Why is that ?
>
> Regards,
> David
>
> > Am 31.01.2019 um 15:46 schrieb Burton, Ross <ross.burton at intel.com>:
> >
> > Please remember to keep the list on CC.
> >
> > The reason is that those recipes are built for the target so they'll
> > be archived, the archiver doesn't distinguish what recipes go into
> > what image.
> >
> > It's relatively simple to filter the list after the build if you want
> > to produce just what is in a specific image, take the image manifest
> > and use oe-pkgdata-util to turn the package names into recipes.
> >
> > Ross
> >
> > On Thu, 31 Jan 2019 at 14:01, David Zimmermann
> > <dzimmermann at yellowtec.com> wrote:
> >>
> >> Hi Ross,
> >>
> >> and thanks for your reply.
> >> I do bake an image based on core-image-minimal with additional packages like openssh and qt (-base, -declarative, -quickcontrols).
> >> My folder ’tmp/deploy/sources/arm-poky-linux-gnueabi’ e.g. contains:
> >> perl, pulseaudio and python
> >>
> >> Even though those might be dependencies I inherited by other recipes - python e.g. is not contained / will be installed to my image.
> >> As a countercheck I see what licenses will be placed in the image (COPY_LIC_DIRS = 1 && COPY_LIC_MANIFEST = 1) which reflects the limited number of packages I do expect.
> >>
> >> Regards,
> >> David
> >>
> >>> Am 31.01.2019 um 11:11 schrieb Burton, Ross <ross.burton at intel.com>:
> >>>
> >>> Does it not just contain the packages used to build the entire image,
> >>> so build-time dependents.  Can you give an example of a recipe that is
> >>> archived but shouldn't be?
> >>>
> >>> Ross
> >>>
> >>> On Thu, 31 Jan 2019 at 08:46, David Zimmermann
> >>> <dzimmermann at yellowtec.com> wrote:
> >>>>
> >>>> Hi List,
> >>>>
> >>>> I use Yocto Krogoth and the following configuration for the archiver:
> >>>>
> >>>> INHERIT += „archiver“
> >>>> COPYLEFT_RECIPE_TYPES = ’target’
> >>>>
> >>>> But the ‚tmp/deploy/sources/…/‚ folder for my target architecture contains much more packages then those ‚used‘ to build my image.
> >>>> Is there a way to extract / archive / isolate only those package sources used for a certain image (kernel + rootfs) ?
> >>>>
> >>>> Thanks for your help,
> >>>> David
> >>>> --
> >>>> _______________________________________________
> >>>> yocto mailing list
> >>>> yocto at yoctoproject.org
> >>>> https://lists.yoctoproject.org/listinfo/yocto
> >>
>