Yocto Project Discussions
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>, poberauer@yahoo.co.uk
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3
Date: Mon, 24 Oct 2022 15:07:11 +0200	[thread overview]
Message-ID: <9101fc7b-aa9e-590d-d4e7-63bb1f09125a@bootlin.com> (raw)
In-Reply-To: <CANNYZj-43o28uUN3nSmspU5M2XbrwnX1VmeSLXJujjQupZANmA@mail.gmail.com>


On 10/24/22 14:27, Alexander Kanavin wrote:
> On Mon, 24 Oct 2022 at 13:58, Peter via lists.yoctoproject.org
> <poberauer=yahoo.co.uk@lists.yoctoproject.org> wrote:
>> However, the documentation recommends the global ban and does not mention the per-image variant?
>> https://docs.yoctoproject.org/ref-manual/images.html
>> https://docs.yoctoproject.org/ref-manual/variables.html#term-INCOMPATIBLE_LICENSE
> Yes, someone should go over the documentation and change every mention
> of this to recommend per-image variant, as a global one is basically
> impossible to use without pulling in meta-gpl2. Patches welcome :)
>
>> Out of curiosity, why does the per image variant work, but not the global ban?
> Global ban works at the task dependency creation stage, and if bash
> needs to be built, it will throw an error, even if the actual bash
> binary will not end up in the image, and is only used as a runtime
> dependency for a package that won't be installed.
> Per-image ban performs a 'late' check when the image is actually put together.
>
> You should now know everything to fix the docs ;-)

Thanks! I should be able to send a patch this week.

Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2022-10-24 13:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 13:27 other ways of removing GPLv3 components (than meta-gplv2) #GPLv3 Peter
2022-10-06 13:46 ` [yocto] " Alexander Kanavin
2022-10-06 16:36   ` Michael Opdenacker
2022-10-07  9:28     ` other ways of removing GPLv3 components (than meta-gplv2) #gplv3 Peter
2022-10-07  9:34       ` [yocto] " Alexander Kanavin
     [not found]       ` <171BBFBB3D98A617.12674@lists.yoctoproject.org>
2022-10-07  9:51         ` Alexander Kanavin
2022-10-24 11:58           ` Peter
2022-10-24 12:27             ` [yocto] " Alexander Kanavin
2022-10-24 13:07               ` Michael Opdenacker [this message]

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=9101fc7b-aa9e-590d-d4e7-63bb1f09125a@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=poberauer@yahoo.co.uk \
    --cc=yocto@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox