All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Mans Zigher <mans.zigher@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] [Question] How to handle GPLv3 packages?
Date: Wed, 6 Apr 2022 11:03:47 +0200	[thread overview]
Message-ID: <CANNYZj_UvDZWC+hD1pjxzkOKK_sL4wB+mu3a8GiPZVwUnEO4iA@mail.gmail.com> (raw)
In-Reply-To: <CAEhQi8=HC7K9XxcCx4e83=JKCG3q=tAb2=BZmfvSqpwt4EG97g@mail.gmail.com>

I'd suggest you start by setting INCOMPATIBLE_LICENSE per image, e.g.
enable gpl3 ban only in the images that ship to the customers and not
across the entire build. Then carefully look at what pulls in bash
into those images and why, and reconfigure those pieces to not do that
(e.g. by reconfiguring the PACKAGECONFIGs), or rewrite the scripts in
posix shell.

Alex

On Wed, 6 Apr 2022 at 10:59, Mans Zigher <mans.zigher@gmail.com> wrote:
>
> Hi,
>
> I cannot use GPLv3 packages in our image build. I am no legal expert
> but from what I can understand most companies will not be able to
> comply with this license without allowing the customer to compile and
> deploy a new version of any GPLv3 package to the target. I know it is
> possible to comply with this but we are using secure boot and have not
> the time and probably no interest in setting up a solution for
> allowing customers to be able to deploy GPLv3 packages on the target.
> We are trying to make use of INCOMPATIBLE_LICENSE but that results in
> several issues. We have made sure that we don't include GPLv3 in the
> image build using a manual process but would like to use
> INCOMPATIBLE_LICENSE to alert any developer about the issue. It seems
> like INCOMPATIBLE_LICENSE is a bit harsh since it will catch any
> packages even if it is only part of the SDK and also for native
> packages that are not part of the image build.
>
> I cannot be the only one with this problem so how are other companies
> solving this issue? Are they just not using the INCOMPATIBLE_LICENSE?
> Are you setting up a parallel process for checking for any
> incompatible licenses issues?
>
> A more specific issue is that there are so many packages with bash
> dependencies which are pulling in bash which is GPLv3 so how have you
> solved that? Currently we have done some pretty uggly hacks which I am
> not that happy with but we needed to keep it out of the image.
>
> Thanks
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#56672): https://lists.yoctoproject.org/g/yocto/message/56672
> Mute This Topic: https://lists.yoctoproject.org/mt/90285507/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2022-04-06 16:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  8:59 [Question] How to handle GPLv3 packages? Måns
2022-04-06  9:03 ` Alexander Kanavin [this message]
2022-04-08  6:06   ` [yocto] " Måns
2022-04-08  8:15     ` Alexander Kanavin
2022-04-08 16:56       ` Måns
2022-04-08 16:59         ` Alexander Kanavin
2022-04-11  7:12           ` Måns
2022-04-11  7:16             ` Alexander Kanavin
2022-04-11  8:29               ` Måns
2022-04-11 16:19                 ` Khem Raj
2022-04-12  9:45                   ` Måns
2022-04-06  9:10 ` Ross Burton
2022-04-08  8:18   ` Måns
2022-04-08  8:22     ` Alexander Kanavin
2022-04-08  8:32     ` Mikko.Rapeli
2022-04-08  9:22       ` Alexander Kanavin
2022-04-08 10:17         ` Måns
2022-04-06  9:23 ` Mikko.Rapeli
2022-04-06  9:31   ` Måns

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=CANNYZj_UvDZWC+hD1pjxzkOKK_sL4wB+mu3a8GiPZVwUnEO4iA@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=mans.zigher@gmail.com \
    --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 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.