All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross@burtonini.com>
To: Mans Zigher <mans.zigher@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [Question] How to handle GPLv3 packages?
Date: Wed, 6 Apr 2022 10:10:59 +0100	[thread overview]
Message-ID: <CAAnfSTvP+aHDxBSSSNVLejxhMPr9NJ4FuYLXDTmaPifBKmGL3w@mail.gmail.com> (raw)
In-Reply-To: <CAEhQi8=HC7K9XxcCx4e83=JKCG3q=tAb2=BZmfvSqpwt4EG97g@mail.gmail.com>

On Wed, 6 Apr 2022 at 09:59, Mans Zigher <mans.zigher@gmail.com> wrote:
> 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.

As you're not naming recipes it is hard to offer concrete advice, but
I will note that a large percentage of the bash dependencies in
oe-core are specific to the ptest packages. If you don't need those
then you can turn off the ptest DISTRO_FEATURE.

Ross


  parent 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 ` [yocto] " Alexander Kanavin
2022-04-08  6:06   ` 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 [this message]
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=CAAnfSTvP+aHDxBSSSNVLejxhMPr9NJ4FuYLXDTmaPifBKmGL3w@mail.gmail.com \
    --to=ross@burtonini.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.