All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Thießen" <christian.thiessen@airbus.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: license manifest files effectively disappear when do_rootfs is not rerun
Date: Mon, 24 Oct 2022 01:58:46 -0700	[thread overview]
Message-ID: <1878.1666601926722962715@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9UMf4FRYzLCN9M+rW-mpL0-JRxROq4zpNd7ABJe5E+Dw@mail.gmail.com>

I'm not deleting anything.
Steps to reproduce would be:
Build just about any image for any machine, as long as it uses the standard classes like license_image.bbclass.
You'll get a build/tmp/deploy/licenses/${IMAGE}-${MACHINE} symlink pointing to build/tmp/deploy/licenses/${IMAGE}-${MACHINE}-<datetime> containing all the expected manifests.
Run the same build again. Bitbake will rerun do_populate_lic_deploy, but not do_rootfs.
build/tmp/deploy/licenses/${IMAGE}-${MACHINE} now points to a new directory that contains only image_license.manifest.

Christian


  reply	other threads:[~2022-10-24  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  8:36 license manifest files effectively disappear when do_rootfs is not rerun Christian Thießen
2022-10-24  8:41 ` [OE-core] " Alexander Kanavin
2022-10-24  8:58   ` Christian Thießen [this message]
2022-10-24  9:40     ` Alexander Kanavin
2022-10-24 11:05       ` Christian Thießen
2022-10-24 11:31         ` [OE-core] " Quentin Schulz
2022-10-25  8:31           ` Christian Thießen
  -- strict thread matches above, loose matches on Subject: below --
2022-10-21 13:31 Christian Thießen
2022-10-25  8:37 ` Christian Thießen

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=1878.1666601926722962715@lists.openembedded.org \
    --to=christian.thiessen@airbus.com \
    --cc=openembedded-core@lists.openembedded.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.